Skip to main content

Requests and Responses

This guide explains the conventions used across all API endpoints. Following these conventions will ensure consistent integrations with Recruso CRM.


Pagination

Most GET endpoints that return lists are paginated.

Request Parameters

Example request:

GET /api/workers?pageNumber=2&pageSize=10

Response Structure

Paginated results use the following format:

{
  "data": [
    { "id": 101, "firstName": "Alice", "lastName": "Smith" },
    { "id": 102, "firstName": "Bob", "lastName": "Jones" }
  ],
  "pageNumber": 2,
  "pageSize": 10,
  "nextPage": "https://api.recruso.co.uk/api/workers?pageNumber=3&pageSize=10",
  "previousPage": "https://api.recruso.co.uk/api/workers?pageNumber=1&pageSize=10",
  "pageCount": 5,
  "totalRecordCount": 48
}

Notes


Error Handling

The API uses a consistent Problem Details format (RFC 7807) for error responses.

Example Error Response

{
  "status": 500,
  "title": "An unexpected error occurred.",
  "instance": "/api/bookings"
}

Fields

Common Status Codes


Time Zone

Conventions


Summary


👉 Next, see the Agencies for details on how agencies are managed.

For a complete list of request and response fields, and to test the endpoints interactively — click below.

Try it