Do we get any indicator in the responses indicating the batch status(if the batch is complete or the no. of candidates pending in the batch)?

Yes, RChilli does provide an indicator in the resume parser response that reflects the batch status of the parsed file, but this is managed in a slightly nuanced way depending on the use case and implementation.

✅ Batch Status Indication in API Response

When using the Resume Parser API, batch-level indicators aren't labeled directly as “Batch Status” but can be inferred and tracked through:

1. filename and subuserid:

   • These fields in the API request help identify and organize batch jobs.

   • The response reflects the same filename and can be logged/tracked for batch processing validation.

2. Processing Summary and Logs (if implemented):

   • When parsing is done in bulk (e.g., via email inbox or zip uploads), your integration can maintain a status log for each file.

   • The API itself returns a valid JSON response for each file parsed—this response can include error messages, missing fields, or parsing errors which serve as indirect indicators of processing status.

3. API Setting Reflection:

   • If you're using Dynamic API Settings, the response includes an apisetting node. This confirms the settings applied for that specific batch job or individual API call.

   • This is useful for batch audits to confirm settings like dateformat, phoneformat, reqeducationdrill, etc., per parsed resume.

4. Error and Status Codes:

   • If there's a parsing issue in a batch, the response JSON includes error indicators or incomplete fields.

   • Your application can interpret these as part of the “status” tracking for the batch job.

🧠 Workaround for Explicit Batch Status Tracking

If your workflow requires an explicit batch status field, consider implementing a custom wrapper or middleware logic that:

• Sends each resume as a batch with a batchID (you define).

• Associates each response with this batchID on your backend.

• Evaluates success/failure by checking for expected fields or presence of error messages in the response JSON.

📌 Summary

While RChilli does not include a field named “Batch Status” by default in the resume parser output, batch processing can be managed and monitored using existing metadata like filename, subuser ID, and API response structure. For precise tracking, it's best to handle batch status externally in your integration or processing logic.

If you need help implementing this kind of tracking or batch identification logic, feel free to reach out to support@rchilli.com or explore the Resume Parser API docs here for technical details.