Returns the account's role offers. Pass a page parameter to receive a paginated envelope; without one, every matching role offer is returned as a flat array.
Set demand_available=1 to return only role offers that still have unfilled demand, which is the usual way to build a list of roles someone can apply for.
This endpoint does not require authentication, but an anonymous caller only receives results on an account that has public browsing switched on.
A filter to apply to the results. Declared as an array of objects, where each object contains an attr (attribute code), operator and value key. Examples:
?filter[0]['attr']=name&filter[0][operator]=like&filter[0][value]=luke
?filter[0]['attr']=id&filter[0][operator]=>&filter[0][value]=265
See the filters documentation for more details on how to use this.
A list of relations to include in the response. May be single records or collections. It is often more efficient to retrieve this way, to avoid follow-up API calls.
- Mock serverhttps://developer.rosterfy.com/_mock/api-docs/openapi/api/v2/headcount/roleoffer
- Your Rosterfy accounthttps://example.rosterfy.com/api/v2/headcount/roleoffer
curl -i -X GET \
'https://developer.rosterfy.com/_mock/api-docs/openapi/api/v2/headcount/roleoffer?demand_available=true&per_page=5&page=1&filter=%7Bfilter%7D&sort_by=%7Bsort_by%7D&sort_order=%7Bsort_order%7D&_locale=en-US&extras=demand&with=functional_area_type' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Rosterfy-Platform: admin'[ { "current_page": 1, "data": [ … ], "first_page_url": "https://example.rosterfy.com/api/v2/headcount/roleoffer?per_page=5&_locale=en-US&page=1", "from": 1, "next_page_url": "https://example.rosterfy.com/api/v2/headcount/roleoffer?per_page=5&_locale=en-US&page=2", "path": "https://example.rosterfy.com/api/v2/headcount/roleoffer", "per_page": 5, "prev_page_url": null, "to": 5 } ]