Requests & Responses
Basics
Use https://api.bedrijfsrooster.nl/api/v2 and the method, parameters, and schema documented for each endpoint.
See Rate Limiting for request limits and Pagination for navigating paginated collections.
Requests
- Send
Authorization: Bearer <access_token>as described in Authentication. - Use query parameters for GET requests; do not send a GET body.
- Send JSON bodies with
Content-Type: application/json. OAuth token requests useapplication/x-www-form-urlencodedinstead. - Follow each field's date format. RFC 3339 timestamps include a timezone offset, for example
2026-10-23T09:00:00+02:00. Some endpoints explicitly accept local date-times in the company's timezone.
Responses
Successful responses contain success: true, metadata, and optional data or message. Collections place their items in data.items. For example:
{
"meta": {
"system": {
"TI_SERVER_TIME": "2026-10-23T07:00:00.000Z",
"TI_SERVER_ID": "-",
"TI_APP_ID": "bedrijfsrooster-app",
"TI_APP_SERVICE": "timeclock",
"TI_APP_DEPLOYMENT_ID": "-",
"TI_APP_VERSION": "2.0.0",
"TI_API_VERSION": "2",
"TI_ENV": "production"
}
},
"success": true,
"data": {
"kind": "TimeclockBadgeCollection",
"items": []
}
}
In v2, version and environment information live in meta.system.TI_API_VERSION and meta.system.TI_ENV; the old top-level apiVersion and env fields are gone. TI_ENV is omitted when the server has no environment configured. Metadata may contain additional fields.
Errors contain error.code and error.message instead of success. Check the HTTP status: 401 indicates missing or invalid authentication; 403 indicates insufficient scope or permissions. Refresh an expired access token; a permissions failure requires correcting the authorization. OAuth token responses follow the provider's standard OAuth format rather than this API envelope.