Retrieve an access clocking

Retrieve an access clocking

Introduction

You can retrieve an access clocking by its ID.

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/{id}

URL parameters

This parameter needs to be filled in when calling this endpoint.

Parameter Description
<id> The internal ID of the access clocking.

Response properties

This list of properties is returned by this endpoint.

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

External references

It’s possible to use predefined external references and custom external references. More information can be found on the External References Page

For a list of predefined external references, see the external reference options section.

Note

Check the query options below the endpoint on the Swagger page for the relevant external references.

Good to know

Time of day

Access clockings always happen on the actual date itself. This is different from other clocking kinds, which have a notion of previous/current/next day.

Note

The timeOfDayInMinutes property for access clockings is limited to values from 0 to 1439 (24 hours), unlike other clockings which support negative values and values above 1440 for overnight clockings.

Status values

A more detailed description of the possible values for the status property.

Value Description
AccessOk Access granted.
AccessRefused Access denied.
WrongPinCode PIN code verification failed.
AlarmCode Alarm code entered (meaning may depend on configuration).
AntiPassbackError Anti-passback rule violated (e.g., required entry/exit sequence not followed).
OutZone Exited a defined zone (floor plan context; may depend on configuration).
UnknownBadge Badge was unknown at the time of clocking. This can be reprocessed if the badge is later linked to a person, but the status remains UnknownBadge.

Examples

Retrieving an access clocking

Example with access clocking ID 1234:

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

With external reference

Example with the employee number as external reference for the person:

GET
https://<tenant>.myprotime.eu/connector/protimeapi/api/v1/access-clockings/1234?externalReferences=(people,@employee-number)