If you want a super-quick win with minimal dev work, RScript drops an “Apply with Resume” experience into your page in minutes. If you need deep control over fields, workflows, and responses, go REST API. Both use the same RChilli parser; the choice is speed vs. flexibility.
When to choose which
-
RScript (fastest go-live)
- Add a button/snippet and auto-fill forms from resumes—setup can be under ~2 minutes. Ideal for pilots, quick POCs, or teams without backend changes.
- Add a button/snippet and auto-fill forms from resumes—setup can be under ~2 minutes. Ideal for pilots, quick POCs, or teams without backend changes.
-
REST API (full control)
- Integrate the Resume Parser endpoints for complete control over request/response handling, mapping, and downstream workflow logic. Same parsing engine, 200+ fields, JSON/XML output. Great for customized ATS/HRIS flows.
- Integrate the Resume Parser endpoints for complete control over request/response handling, mapping, and downstream workflow logic. Same parsing engine, 200+ fields, JSON/XML output. Great for customized ATS/HRIS flows.
For more information visit this link: Resume Parser API (overview)
For assistance with configuration, contact: support@rchilli.com
Comments
0 comments
Please sign in to leave a comment.