Retrieve a list

Returns a filtered list of access clockings.

Tip

Check the Swagger page for more technical information on the endpoints.

Endpoint details

GET
https://<tenant>.myprotime.eu/connector/protimeapi/api/v1/access-clockings

Headers: Authorization: Bearer {token}, User-Agent: {agent} Scope: connector-protimeapi-access-clockings.read

Response properties

Field Type Required Writable Description
changeVersion string — Read-only Property to indicate the order of changes.
id integer — Read-only Unique identifier for the access clocking.
person.id integer — Read-only Internal ID of the person who performed the clocking.
date string — Read-only Date of the access clocking (YYYY-MM-DD).
timeOfDayInMinutes integer — Read-only Minutes since midnight (0 to 1439) representing the time of the clocking on the specified date.
terminal.id integer — Read-only Internal ID of the terminal on which the clocking occurred.
status string — Read-only Result of the access attempt (AccessOk, AccessRefused, WrongPinCode, AlarmCode, AntiPassbackError, OutZone, UnknownBadgeNumber).

Filters

Filter Type Description
person Optional Internal person IDs (person in (1, 2, 3)), or the current members of circles (person in circle(2, 8)) or org-groups (person in org-group(121, 122)). When omitted, all people are returned.
date Required Date range (required with max of 1 year range)

Note

  • The person filter cannot be combined with delta. A request with both returns 400 Bad Request.
  • With a person filter, results are paged per 100 people. If the people matched by the filter change between pages (for example, a circle or org-group membership change), the next page returns 409 Conflict; restart from the first request.

Check the Fetching Resources page on how to use the filter.

External references

The endpoint supports predefined and custom external references. See the external references page for details.

The following collections are supported for this endpoint:

Collection Predefined Custom
people @badge-number, @employee-number Supported
terminals @external-code Supported

Caution

There are some restrictions on the characters allowed in URL requests. See the fetching resources page for more information.

Error responses

Status Condition
400 Invalid filter syntax, unknown filter field, or a person filter combined with delta
401 Missing or invalid access token, or insufficient scope
409 The people matched by the person filter changed between pages
414 Request URI too long (filter + continuation token)

Examples

Filter on date range

Example with a date range:

GET
https://<tenant>.myprotime.eu/connector/protimeapi/api/v1/access-clockings?filter=date ge '2025-01-01' and date le '2026-01-01'

Filter on people and a date range with external reference

Example with people, a date range and the employee number as an external reference:

GET
https://<tenant>.myprotime.eu/connector/protimeapi/api/v1/access-clockings?filter=person in (1,2,3) and date ge '2025-01-01' and date le '2026-01-01' &externalReferences=(people,@employee-number)