FAQ
- Can I delete test or sample data from the Search & Match environment?
- What happens if we exceed our monthly API usage limit? Will the parsing stop?
- How does the parser handle resumes written in Arabic or other languages using OCR?
- Can the parser understand if someone is still working at a company when the CV only says ‘till now’ or ‘currently’?
- Can I submit one job description and match it with thousands of resumes automatically?
- Can we do a bulk upload of resumes from our email threads directly into the parser?
- Can you share reports that show how many CVs we’ve parsed over a certain period?
- How can I make sure certain personal information like names or contact details are hidden from recruiters?
- Is it possible to match candidates based on skills, even if the job title is niche or uncommon?
- How can I cancel my RChilli subscription?
- Can RChilli match resumes to job descriptions and provide a matching score?
- Why Am I Getting Too Many Duplicate Entries in Search Results - Search and Match?
- How Do I Know if My Resume Parsing is Correctly Capturing Skills from Job Experience?
- Can I Get a Breakdown of How the Matching Score is Calculated for a Specific Candidate-Job Pair?
- Why Am I Getting the Same Score When Toggling degreeWithSpecialization' in Some Matches?
- Does the “degreeWithSpecialization” parameter in matching API always affect the scores?
- Is there a way to trigger data reprocessing from our side or does RChilli handle that?
- How do I troubleshoot "Resume Parsing succeeded but containers not found" errors?
- Why am I seeing an error that says “RChilli API Database does not exist” even though it's installed
- Is there a limit to the number of resumes that can be parsed simultaneously using RChilli?
- Why can't I see the updated profile or email even after making changes?
- Can I change the email ID linked to my account or organization?
- Our integration suddenly stopped working—what should we check first before escalating?
- Why am I getting a 200 status code but the actual response body shows a 404 error?
- Can we customize weightage in Search & Match to prioritize certain attributes like skills or education?
- Is there a REST API that allows changing these settings (e.g., toggling OCR or skill types) programmatically from their application, without logging into RChilli’s dashboard?
- Can parsing configurations (like enabling/disabling OCR or specific skill types) be modified dynamically per API call, or are these global settings that must be manually adjusted in the dashboard?
- Is the 0.3 credit for taxonomy usage charged per skill, or is it a one-time 0.3 credit per resume, regardless of the number of skills parsed?
- Is it possible to limit the number of skills returned from a parsed CV or job description? Can clients filter skills based on interest (e.g., exclude generic terms like “developer”)?
- Can the normalization process for JD parsing be customized? Specifically, can it extract or prioritize only specific skills—like including “Python” but excluding variants such as “Python 3.x”?