Pagination

Default behaviour

Public list endpoints return at most 20 items per request. Use the page and limit query parameters to navigate:

GET /api/v1/jobs?page=2&limit=20

The same pattern applies to GET /api/v1/events, GET /api/v1/posts, and bearer-authenticated dealer lists:

Response shape

Paginated responses nest results and metadata inside the data envelope. The collection key matches the resource name:

{
  "data": {
    "jobs": [ ... ],
    "total": 142,
    "page": 2,
    "pages": 8
  }
}

For events and posts, the collection key is events or posts respectively:

{
  "data": {
    "events": [ ... ],
    "total": 42,
    "page": 1,
    "pages": 3
  }
}

Limits

Filtering

List endpoints accept filter query parameters. Supported fields differ by resource — refer to the API Reference for each endpoint's schema.

Jobs support free-text search via q (max 200 characters) plus filters such as category, department, contractType, city, and salary bounds. Events and posts support q for search.

There is no sort or order parameter on the public v1 contract.