Can we send a batchID in the request? Or should we consider 'subuserid' as a batchId?

You can send a batchID in the request, but in RChilli's API context, the subuserid parameter is typically used as a unique identifier for the batch or client sub-user. So effectively, you can consider subuserid as serving the role of a batch ID to differentiate requests or track them uniquely.

Explanation:

• The subuserid is a required field in RChilli's Resume Parser API request, used as your unique sub-user identifier to track and manage API usage.

• There is no explicit separate batchID parameter documented in the API for batch identification.

• Hence, if you want to send or track batch requests, you should use the subuserid field to represent your batch or logical grouping of requests.

Example from Resume Parser API JSON request:
{
"filedata": "{{base64data}}",
"filename": "{{filename}}",
"userkey": "{{userkey}}",
"version": "8.0.0",
"subuserid": "{{subuserid}}"
}

Here, subuserid is the unique ID you set per batch or sub-client for request tracking.