How many record can a client get in a Search Query?

RChilli’s Search & Match API supports pagination, which allows clients to retrieve results in manageable chunks when dealing with large datasets. However, the exact number of records returned per search query depends on how pagination is configured in the API request.

Default and Configurable Record Limits

By default, the number of records returned per page (i.e., one search API call) is typically 10 results, especially when using the standard Search & Match configuration.

You can adjust this using the limit and offset parameters:

• limit: defines how many records you want per page.

• offset: determines the starting point for the records to fetch (used for pagination).

For instance, to retrieve the first 20 results:

{
  "searchquery": "Java Developer",
  "limit": 20,
  "offset": 0
}

To fetch the next set of 20:

{
  "searchquery": "Java Developer",
  "limit": 20,
  "offset": 20
}

This way, clients can retrieve as many records as needed by paginating through the result set.

Key Features Supporting Bulk Retrieval

• Pagination support ensures performance and usability with large datasets.

• Top N results logic is used in ranking matches by relevance (e.g., top 10 or top 50 candidates).

• The engine processes bulk data efficiently using scalable architecture.

Helpful Reference

More details on this are documented under RChilli’s Search & Match capabilities and can be explored in the Search & Match API documentation.

If you require retrieving a very large dataset (e.g., 1000+ candidates) in a single session, it's best to use pagination and potentially combine it with filtering criteria (e.g., by location, skills, etc.) to improve performance.

If you need help implementing or optimizing this in your system, feel free to contact support@rchilli.com.