RChilli does not have the functionality to use raw data with the Match API. The system only supports matching RChilli JSON Output for the following reasons:
Why Raw Data is Not Supported for Matching:
-
Credit Usage:
If raw data were allowed for matching, parsing credits would be consumed each time a matching request is made. This would lead to unnecessary parsing charges if the same resumes or job descriptions were matched repeatedly. -
Optimization:
By using the RChilli JSON Output, we ensure that parsed data is stored in a structured format, which prevents multiple parsing requests for the same resumes and allows for more efficient and cost-effective matching.
How RChilli Match APIs Work:
-
The Search & Match API works by taking pre-parsed JSON data and comparing it to other job descriptions or resumes. The API is designed to use structured data that has already been processed to avoid re-parsing and to ensure accurate and fast matching.
-
JSON Output: The output from the RChilli Resume Parser or Job Description Parser is structured and enriched, containing all necessary fields like job titles, skills, education, experience, etc., which the Match API uses for effective matching.
How to Use the Match API with JSON Output:
To use the Search & Match API with JSON output, follow these steps:
-
Parse Data:
First, parse the raw resume or job description using RChilli’s Resume Parser or Job Description Parser.API:
-
Get JSON Output:
The output will be a structured JSON document containing all the parsed details such as skills, experience, education, and job titles. -
Use the Match API:
Once the data is parsed, pass the structured JSON output to the Search & Match API for matching.API Documentation:
-
Optimize Matching:
After matching, the results will include match scores, rankings, and facet filters based on the structured data.
Need More Help?
For further inquiries or if you need assistance with API implementation, feel free to contact RChilli Support by creating a Helpdesk ticket or emailing us at support@rchilli.com.
Comments
0 comments
Please sign in to leave a comment.