Why did my request get corrupted when parsing certain resumes? – RChilli HelpDesk

This issue typically occurs when the resume file format, encoding, or content doesn't align with the expected structure of the RChilli Resume Parser API.

Common Reasons for Request Corruption

Cause	Description
Unsupported File Format	RChilli supports DOC, DOCX, PDF, RTF, TXT, ODT, HTML, and a few others. Uploading unsupported or corrupt files (e.g., images embedded in DOC) may lead to malformed or partial responses.
Incorrect Base64 Encoding	When parsing via binary (filedata), ensure the resume is properly base64-encoded. Incorrect encoding may result in truncation or unreadability.
Special Characters or Corrupt Encoding	Resumes with non-UTF8 characters or invalid escape sequences can break the parser input.
Empty or Blank Files	Submitting empty files (even valid formats) may cause the API to return errors or incomplete JSON responses.
Incorrect JSON Structure	If the API request body is malformed (e.g., missing braces or incorrect parameter names), the server may reject it or respond with an error embedded in a 200 response.

How to Fix or Avoid This Issue

1. Validate File Type

Ensure that your resume files are in supported formats such as: .doc, .docx, .pdf, .rtf, .txt, .odt, .html, .htm.
Avoid uploading scanned image files unless OCR capabilities are enabled.

2. Use Proper Base64 Encoding

Ensure the binary file is properly base64-encoded when submitting in the filedata field. Here's an example:

{

"filedata": "base64-encoded-content",

"filename": "resume.pdf",

"userkey": "your_user_key",

"version": "8.0.0",

"subuserid": "your_subuser_id"

}

3. Sanitize Resume Content

Remove corrupt characters or invalid escape sequences from .txt or .html files.
Ensure that multi-language files use UTF-8 encoding.

4. Log and Review Responses

Always log both the request and response for debugging purposes. Pay attention to fields such as error.message or ResumeParserData being null or empty.

5. Use Retry with Sample Validation

If parsing fails, try submitting a known good resume to verify that the issue lies with the file and not the API integration.

Helpful Documentation

Still Stuck?

If you're unable to resolve the issue, please send the failing resume file and API request (with sensitive data masked) to: support@rchilli.com. Our team will help you diagnose the root cause and recommend solutions.

Related articles