How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Clockify Entity changes (Experimental) API

For use case see [Entity Changes Use Cases](#tag/Entity-Changes:-Use-cases)

Clockify Entity changes (Experimental) API is one of 28 APIs that Clockify publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Entity changes (Experimental). The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.clockify.me/api/v1.

3 operations 3 paths 2 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.clockify.me/api/v1
Authentication
API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 4

Clockify Entity changes (Experimental) API declares 4 security schemes for authenticating requests. An API key is passed in the header as x-addon-token (AddonKeyAuth). An API key is passed in the header as x-api-key (ApiKeyAuth). An API key is passed in the header as x-marketplace-token (MarketplaceKeyAuth). An API key is passed in the header as x-addon-token (ReportAddonKeyAuth).

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Entity changes (Experimental) 3

For use case see [Entity Changes Use Cases](tag/Entity-Changes:-Use-cases)

GET
/v1/workspaces/{workspaceId}/entities/created
Created entities (Experimental)
getCreatedEntityInfo 6 params → 200
GET
/v1/workspaces/{workspaceId}/entities/deleted
Deleted entities (Experimental)
getDeletedEntityInfo 6 params → 200
GET
/v1/workspaces/{workspaceId}/entities/updated
Updated entities (Experimental)
getUpdatedEntityInfo 6 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are LogBinDocumentDto (4 properties), PageableCollectionLogBinDocumentDto (1 property). Each schema is shown below with its type and property counts.

LogBinDocumentDto
object
4 properties
PageableCollectionLogBinDocumentDto
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clockify-entity-changes-experimental-api-openapi.yml Raw ↑

Other APIs Clockify publishes across the network.

Clockify REST API
Clockify Approval API
Clockify Audit Log Report API
Clockify Balance API
Clockify Client API
Clockify Custom fields API
Clockify Expense API
Clockify Expense Report API
Clockify Group API
Clockify Holiday API
Clockify Invoice API
Clockify Policy API
Where this information came from

This is an independent, third-party profile of Clockify Entity changes (Experimental) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.