Overview
Any data you interact with via the Bindbee API can be paginated, and this pagination is determined by thecursor and page_size query parameters.
Sample HTTP Request
Above is an example of an interactive HTTP request using the Bindbee API to demonstrate how pagination works:Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Query Parameters
The ID of employees to fetch
The ID of managers to fetch employees for
The third-party API ID of the matching object.
The ID of companies to fetch employees for
Whether to include the original data Bindbee fetched from the third-party to produce these models.
Whether to include custom fields in the response.
If provided, will only return employees with this employment status.
ACTIVE, PENDING, INACTIVE, ACTIVE_EXTERNAL, INACTIVE_EXTERNAL If provided, will only return employees for this employee number
The ID of groups to fetch employees for
Number of results to return per page. Maximum size is 100.
1 <= x <= 100The pagination cursor value.
If provided, only objects synced by Bindbee after this date time will be returned. Format: DateTime (ISO 8601)
Which relations should be returned in expanded form. Multiple relation names should be comma separated without spaces. You can also specify required fields in [] for each relation name.