post https://api.adept-id.com/v2/parse-resume
Parse a resume into AdeptID's Candidate Schema in preparation for matching and scoring.
Recipes
📄
Parse and Evaluate
Open Recipe
Use this endpoint to parse a Candidate and their Contact Info from a resume. The resulting Candidate object can be used across AdeptID's Matching family of endpoints, and the Contact Info can be saved by the user for future reference.
Note: This is a value-added service and is not available by default. To access this service, please contact your AdeptID Partner Success team.
Additional Notes:
- This is a synchronous endpoint with a latency of multiple seconds in some scenarios. Users should consider this when configuring API timeout limits.
- The resume must be in the format of a standard 'base64' encoding as defined in RFC 4648 Section 4 (not the 'base64url' variant). The encoded files can be PDF, doc, docx, HTML, rtf, txt, odt, Apple iWork Pages, or plain-text.
- Within the payload, users must identify a
document_last_modified_date. When writing a resume, candidates will typically list their most recent work and/or education experience with an end date of "present", "current", or something similar. Using thedocument_last_modified_date, AdeptID can better interpret those experiences.
Tips:
- While most PDFs will successfully parse, other document types (e.g., .doc, HTML) are less likely to corrupt and result in an unsuccessful parse. AdeptID recommends formats other than PDF when available.
- Parsers often struggle with complex formats/layouts. AdeptID recommends a simple, standard resume format similar to "Jake's Resume" on Overleaf.
- Long resumes with many pages, like those seen in academia, might list numerous academic and research items (e.g., publications). If these items are listed alongside the name of an education institution, parsers may interpret them as degree programs.