Affinda Resume Parser
The Resume Parser reads a resume and returns it as structured JSON: the person, their contact details, work history, education, certifications, skills and languages, along with what the parser made of the document itself.
It is one HTTP request. There is no upload step, no job to poll and no callback.
POST https://resume-parser.affinda.com/v1/resumes/parse
Nothing is stored. The parser keeps no copy of your file and no record of the result, so there is nothing to fetch, list or delete afterwards. If you need the result, keep the response.
Send a PDF, a Word or OpenDocument file, an image, plain text, HTML or RTF, up to 20 MB. One successful parse costs one credit, however many pages the document has, and a failed parse costs nothing.
Two ways to run it
The cloud API. Create an API key in the console and post files to
resume-parser.affinda.com. There is nothing to install. Start with Quickstart.
The self-hosted container. Run affinda/resume-parser on your own infrastructure. The
documents never leave your network, the container is licensed rather than metered per request,
and it answers the same path with the same JSON. See Self-hosted.
The two are deliberately the same request. Moving between them is a change of base URL and authentication, and nothing else.
Regions
The cloud API runs in three regions, each its own deployment.
| Region | Host |
|---|---|
| Asia Pacific | resume-parser.affinda.com |
| United States | resume-parser.us1.affinda.com |
| Europe | resume-parser.eu1.affinda.com |
Your account, your credits and your API keys live in the region you signed up in. Use the host for that region. See Regions.
Getting a key
Sign in to the console on the host for your region and open the API keys screen at /keys.
New accounts start with a 14-day trial of 1,000 free documents. Authentication
covers how keys work, and Errors and limits covers what a credit buys.
To see the output before you write any code, the free tool on our website at https://www.affinda.com/free-resume-parser parses a resume in your browser with no account, up to a generous daily fair-use cap.
Where to go next
- Quickstart: your first parse, in curl, Python or TypeScript.
- Authentication: API keys, where they work and where they do not.
- API reference: every parameter, header and status code.
- The parse response: a guided tour of the JSON.
- Errors and limits: the error envelope, rate limits and credits.
- Self-hosted: running the container yourself.