This behavior generally should not occur. RChilli APIs are designed to return a 200 OK status only when the request is successfully processed, and appropriate error codes are returned in the HTTP response when an error occurs—such as 400, 401, or 404—as per the API documentation.
However, if you are seeing a 200 status with a 404 error inside the response body, it may be due to:
- An incorrect or invalid parameter in the API request (e.g., wrong userkey, version, or subuserid)
- A non-existent resource being referenced (e.g., an inaccessible file URL)
- API middleware capturing the error and embedding it inside the response body instead of triggering a true HTTP 404 status
📌 Recommendation:
- Review the "error" or "status" field in the JSON response body.
- Double-check all request parameters.
- Refer to the RChilli Resume Parser API Error Codes for expected behavior.
If the issue persists, please contact support@rchilli.com with your request payload and response for further analysis.
Comments
0 comments
Please sign in to leave a comment.