How can connection errors be troubleshot when using the RChilli Resume Parser API?

Connection errors can occur because of an incorrect endpoint, invalid authentication details, unsupported parser version, request-format issues, network restrictions, or account configuration.

Follow the steps below to identify the cause.

Step 1: Confirm the API Endpoint

Verify that the application is calling the Resume Parser endpoint configured for the account and deployment region.

Current REST endpoints include:

Resume Binary Data

https://rest.rchilli.com/RChilliParser/Rchilli/parseResumeBinary

Resume Public URL

https://rest.rchilli.com/RChilliParser/Rchilli/parseResume

The Resume Parser API uses the POST method and returns JSON responses.

Step 2: Verify the Parser Version

Check the version value in the API request.

Current documentation and sample requests use: 8.0.0

The parser version must also be supported by the applicable account agreement.

An unsupported or unauthorized version can result in version-related errors.

Step 3: Validate Authentication Details

Verify the following request parameters:

userkey

subuserid

version

Confirm that:

userkey is valid and active.
subuserid matches the configured account information.
version is supported.
No spaces are included in the Sub-User ID.

Step 4: Check the Request Format

For REST API requests:

Use the POST method.
Set Content-Type to application/json.
Send properly formatted JSON.
For binary resume parsing, send resume content as Base64 data.
Include the complete filename with the file extension.

Compare the request with the documented Resume Parser request examples before retesting.

Step 5: Test Connectivity Outside the Application

Run the same API request through:

Postman
cURL

This helps determine whether the issue is related to the API request or the application implementation.

If Postman or cURL succeeds while the application fails, review the application network and request configuration.

Step 6: Review Network and TLS Settings

Verify outbound HTTPS connectivity to the RChilli API endpoint.

Check:

Firewall rules
Proxy settings
VPN configuration
DNS resolution
SSL/TLS inspection
Certificate trust
Connection timeout settings

Network security controls should allow HTTPS communication with the configured RChilli endpoint.

Step 7: Review the HTTP Status and API Response

Capture the complete HTTP status code and API response.

Check for messages related to:

Invalid or expired User Key
Missing required parameters
Invalid parser version
Version not supported by the account agreement
Invalid JSON
Exhausted parsing credits

The response message can help identify whether the issue is related to authentication, configuration, request format, or account access.

Step 8: Confirm Account and Server Configuration

RChilli supports account-specific server locations.

Verify that the API request is being sent to the server configured for the account.

A server-location change may require assistance from RChilli Support.

Step 9: Escalate with Diagnostic Details

If the connection error continues, provide the following information to RChilli Support:

Request timestamp and time zone
API endpoint
Parser version
HTTP status code
Complete error response
Request ID, when available
Sample API request with credentials and resume data removed
Postman or cURL test results
Recent firewall, proxy, certificate, network, or application changes

Sensitive credentials and resume data should not be included in diagnostic information.

Important

Current referenced RChilli documentation describes the REST Resume Parser API and parser version 8.0.0.

The SOAP WSDL endpoint and parser version 6.0.0 are not included in the current referenced documentation. Existing integrations still using version 6.0.0 should confirm the supported endpoint and migration path with RChilli Support before making production changes.