# Bedrijfsrooster Developers Documentation > Official guides and API v2 reference. Set up Bedrijfsrooster Connect, authorize with OAuth 2.0 Authorization Code and PKCE, and test with Postman. ## Guides - [Bedrijfsrooster Developer Hub](https://developers.bedrijfsrooster.nl/docs): Build integrations with the Bedrijfsrooster API using OAuth 2.0 and the recommended **v2 endpoints**. - [Setup Bedrijfsrooster Connect](https://developers.bedrijfsrooster.nl/docs/create-a-customer-api-user): Create a Connect user for each external application that needs access to your company's Bedrijfsrooster data. A company owner must authorize the connection. - [Authentication](https://developers.bedrijfsrooster.nl/docs/authentication): Use OAuth 2.0 Authorization Code with PKCE through **accounts.bedrijfsrooster.nl** to connect to the Bedrijfsrooster API. Use the **v2 endpoints** at `https://api.bedrijfsrooster.nl/api/v2` for integrations. Legacy IAM is deprecated; password and client-credentials grants are not supported for external integrations. - [Requests & Responses](https://developers.bedrijfsrooster.nl/docs/json-request-response-format): Use `https://api.bedrijfsrooster.nl/api/v2` and the method, parameters, and schema documented for each [endpoint](https://developers.bedrijfsrooster.nl/reference). - [Rate Limiting](https://developers.bedrijfsrooster.nl/docs/rate-limiting): Use the response headers to track your request allowance. Limits can vary by service. - [Pagination](https://developers.bedrijfsrooster.nl/docs/pagination): Collection endpoints that support pagination accept `itemsPerPage` and `pageIndex` as query parameters. Page numbering starts at **1**. For the company timetable, `itemsPerPage` defaults to **1000** and accepts values from **1 to 1000**. For example, request the first page of up to 100 shifts with: - [Test with Postman](https://developers.bedrijfsrooster.nl/docs/postman): Test API v2 with one ready-to-import Postman collection and separate Production and Local environments. OAuth settings are already configured. - [MCP Access for Clankers](https://developers.bedrijfsrooster.nl/docs/mcp-access): Bots, AI agents, and other clankers can already use the Bedrijfsrooster API. They connect the same way as any other integration: through a [Connect user](./create-a-customer-api-user.md) and the OAuth 2.0 flow described in [Authentication](./authentication.md), then call the **v2 endpoints**. ## Downloads - [Postman templates (.zip)](https://developers.bedrijfsrooster.nl/assets/files/bedrijfsrooster-postman-imports.zip): API v2 collection, Production and Local environments, and setup instructions. ## Company Feeds - [Timetable Feed](https://developers.bedrijfsrooster.nl/reference/TimetableFeed.md): Get a detailed ShiftCollection snapshot for the Company Timetable, by default for the day on which the request is made. Query the calendar on a specific day by adding the date parameter, from -8 day to +38 days ranging the current date. ## Company - [getConfiguration](https://developers.bedrijfsrooster.nl/reference/getConfiguration.md): Get a configuration object for the Company related to your access token. This object contains information about the primary entities in a Company. Entities can be linked to the related ID provided in other Company API endpoints like /timetable. - [getCompanyUsers](https://developers.bedrijfsrooster.nl/reference/getCompanyUsers.md): Get a CompanyUserCollection for the Company related to your access token. Company Users are employees that have an active or future employment at the company at the time of the request, or within the period as specified by parameters. - [getCompanyContracts](https://developers.bedrijfsrooster.nl/reference/getCompanyContracts.md): Get a CompanyContractCollection for the Company related to your access token. Company Contracts are the agreements between a Company and its employees, active at the time of the request, or within the period as specified by parameters. - [getTimetable](https://developers.bedrijfsrooster.nl/reference/getTimetable.md): Get a ShiftCollection for the Company Timetable related to your access token. Shifts are schedule related objects like employee work times, availability, relief and absence registrations. - [createRevenue](https://developers.bedrijfsrooster.nl/reference/createRevenue.md): Process a batch of revenue items. This can be either realised revenue or a prognosis, on a daily or weekly basis, or both. - [createWageBudget](https://developers.bedrijfsrooster.nl/reference/createWageBudget.md): Process a batch of wage budget items. This should be values on a daily or weekly basis, or both. - [getCompanyReport](https://developers.bedrijfsrooster.nl/reference/getCompanyReport.md): Get one finished report of the Company related to your access token, by its `reportId`. A report is a computed Bedrijfsrooster rapportage (for example `companyReliefHours`, the year balance of relief hours) that the app generated earlier; this returns its stored result exactly as the app receives it, under `Data`. The shape of `Data` depends on the report's `typeConstant`. A report that is not finished yet is an error, not a partial result: HTTP 409 with the progress inside the message as `percentage_complete []` (integer 0-100), so poll again later. A report that belongs to another company answers 403; an unknown or deleted `reportId` answers 404. Requires the `company:reports:read` integration permission in addition to the OAuth `ti_api_usr` scope. - [getCompanyAvailability](https://developers.bedrijfsrooster.nl/reference/getCompanyAvailability.md): Get the availability ("beschikbaarheid") of the Company related to your access token over one month, per date. This returns the same numbers as the Bedrijfsrooster databrowser availability report under "Capaciteit > Beschikbaarheid": per CompanyUser the total available hours per date, or per CompanyFunction the headcount of available CompanyUsers per date. Beyond the report, each date is also broken down: for `entity=companyUser` the exact timespans that make up that date's total hours, and for `entity=companyFunction` the date split into concurrency segments — windows over which the number of simultaneously available CompanyUsers is constant. Both breakdowns use full local date-times (`YYYY-MM-DD HH:MM:SS`) rather than times of day, because an availability window can run past midnight. Such a window is attributed in full to the date it STARTS on, so a consumer must not also count it under the following date. The `entity` parameter is required and selects which of the two collections is returned. Requires the `company:availability:read` integration permission in addition to the OAuth `ti_api_usr` scope. ## Timeclock - [getTimeclockBadgeCollection](https://developers.bedrijfsrooster.nl/reference/getTimeclockBadgeCollection.md): Get the registered timeclock badges for active employees, managers, and owners in the authorized company group. The response is not filtered by companyId; filter data.items in your application if needed. - [createTimeclockEvent](https://developers.bedrijfsrooster.nl/reference/createTimeclockEvent.md): 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.