Pagination

All list-based endpoints (e.g. jobs, users, candidates, threads) support pagination to improve performance and manage large datasets.

Recruspace uses page-based pagination with optional control over page and page_size. By default, different endpoints may have different limits depending on usage context.

🔁 Query Parameters

page – (optional) The page number to retrieve. Starts at 1.

page_size – (optional) Number of results per page. Maximum allowed is 100. If not provided, the endpoint's default value is used.

📌 Example Request

The following example retrieves job posts for a company using pagination:

page=2 → Returns the second page of results.
page_size=9 → Limits the results to 9 items per page.

✅ Example JSON Response

{
  "count": 27,
  "next": "https://api.recruspace.com/companies/<your_company_id>/job-posts-list/?page=3&page_size=9",
  "previous": "https://api.recruspace.com/companies/<your_company_id>/job-posts-list/?page=1&page_size=9",
  "results": [
      {
        "hash": "13gfsa23s1a5sf3f63",
        "applicant_count": 10,
        "example_candidates": [
          {
            "id": 1234,
            "email": "example@mail.com",
            "first_name": "example_first_name",
            "last_name": "example_last_name",
            "photo": null
          },
    // ...
  ]
}

count: Total number of items (in this case, there are 27 job posts).

next: The URL for the next page of results. If you’re on the last page, this field will be absent.

previous: The URL for the previous page of results. If you’re on the first page, this field will be absent.

results: The list of items. In this example, it shows job post details.

🔁 Query Parameters#

📌 Example Request#

✅ Example JSON Response#

🔁 Query Parameters

📌 Example Request

✅ Example JSON Response