The maximum number of records that can be returned in a single API call varies depending on the specific RChilli API in use. Here are the key points:
For Resume Parsing APIs
RChilli Resume Parser APIs are typically designed to handle one resume per API call. However, you can perform bulk parsing using integrations like:
-
Email inbox parsing
-
Bulk uploads via zip files
-
Partner feed integration
These methods process resumes sequentially but may appear as bulk due to automation—still, each call processes a single file at a time behind the scenes.
For Search & Match API
The Search & Match API supports returning multiple records, and the results are paginated for better performance:
-
You can control the number of records returned by setting the
countparameter in your API request. -
The maximum recommended value for
countis typically 100 per page, though this may be adjusted based on your subscription or implementation specifics. -
Pagination is implemented using parameters like
startandcount.
If you're processing large datasets, you should implement pagination logic to retrieve results in chunks rather than all at once.
Resume Templater API
This API processes one resume at a time (with each request consuming 2 parsing credits) and returns a formatted template version. It’s not optimized for bulk output in one API call.
Workaround for Bulk Needs
To efficiently handle large volumes:
-
Use batch automation in client apps.
-
Use zip file uploads or multi-threaded request handling.
-
For large dataset indexing/search, implement pagination with count/start parameters in Search & Match.
Need Help Configuring?
If you're looking to increase limits or enable true bulk processing, contact support@rchilli.com
If you have any questions or concerns, please don't hesitate to reach out to us at support@rchilli.com
Comments
0 comments
Please sign in to leave a comment.