createTimeclockEvent
POST/timeclock/events
Process a new timeclock event registered via the Bedrijfsrooster App or hardware devices. Always make sure that creating events related to a specific person is done in chronologically ordered requests. Each request should receive a 200 OK response before you can send the next time based event for the same person. The target company must have timeclock and external terminal input enabled, and the request must satisfy its IP restrictions.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
- 504
Timeclock event processed. Returns success and a message; no data object.
Invalid request data.
Access token missing, invalid or expired.
Response Headers
Points to protected-resource metadata when authentication is missing.
Bearer resource_metadata="https://api.bedrijfsrooster.nl/.well-known/oauth-protected-resource"The access token lacks the required scope, or the authorized user or integration does not have permission to access this company or resource.
Either the requested route does not exist, or (for these proxied routes) the legacy PHP backend reported the requested resource as not found.
Request rate limit exceeded. See the X-RateLimit-* and Retry-After response headers for details. Timeclock is the only v1 service that historically shipped a custom TI_INSTANCE_RATELIMITER_CONFIG_JSON, so its actual points/duration may differ from the library default shown in this example.
Response Headers
Maximum number of requests allowed per window (default 25).
Number of requests remaining in the current window.
Milliseconds until the current window resets.
Seconds to wait before retrying.
An unhandled error occurred. Internal error detail is never echoed on 5xx responses — this generic message is always used instead.
The upstream service did not respond before the request deadline.