Curriculo's resume parser API turns a PDF or DOCX CV into structured JSON (contact details, job title, roles with dates, education and skills) with one POST request, for $0.01 per CV. If you're building an ATS, job board, or HR tool, parsing is often the base your other features need. Here it takes one API key from the Developer Console and no ATS login.
Quick facts
- PDF and DOCX
- 10 per request
- $0.01 per CV
- $5 free credit
- Sync parse is stateless
Request
curl -X POST https://api.curriculo.me/public/parse/ \
-H 'Authorization: Bearer key_abc123_yoursecret' \
-F 'files=@/path/to/candidate.pdf'Response
{
"name": "Jordan Rivera",
"title": "Lead Software Engineer",
"email": "[email protected]",
"experience": [ ... ],
"technical_skills": [ ... ]
}Get your API key or read the full API reference.
What does the resume parser API return?
One JSON record per CV, with the candidate's name, contact details, job title, roles with dates, education, and skills. Missing fields come back empty, and list fields are always arrays.
{
"name": "Jordan Rivera",
"title": "Lead Software Engineer",
"email": "[email protected]",
"experience": [ ... ],
"technical_skills": [ ... ]
}Values stay in the CV's own language and script, with nothing translated or rewritten. Field details are in the full API reference.
How do you parse a resume with the API?
You need an API key from the Developer Console and one multipart POST to /parse/, with the CV in the files field.
Sign in at console.curriculo.me. A one-time $5.00 credit is added to your account.
Open API keys and choose Create API key. The key looks like
key_<id>_<secret>and is shown once, so store it before you leave the page.Send the request:
curl -X POST https://api.curriculo.me/public/parse/ \ -H 'Authorization: Bearer key_abc123_yoursecret' \ -F 'files=@/path/to/candidate.pdf'
You can also run a sync parse on a real resume from the Console's docs page before you write any code. Next: Quickstart and the full API reference.
Can you parse CVs in bulk?
Yes. Send up to 10 documents in one request and the results come back as an array in input order. For a backlog, POST /parse/async takes up to 25 links per task.
curl -X POST https://api.curriculo.me/public/parse/ \
-H 'Authorization: Bearer key_abc123_yoursecret' \
-F 'files=@candidate_a.pdf' \
-F 'files=@candidate_b.docx'A failed document returns its own error and doesn't fail the rest. Each file can be up to 10 MB and the request body up to 12 MB. A 413 means a document over 10 MB, more than 10 documents, or a body over 12 MB.
Timing for large batches is in the rate limits section below. Both options are documented in Batching.
What are the rate limits?
600 requests a minute per API key. Each parse takes about 40 to 90 seconds, and sustained throughput is about 2 to 4 CVs a minute.
Set your client timeout above five minutes, because a request that passes 300 seconds returns a 504. Send backlogs through /parse/async. See Rate limits.
How much does the resume parser API cost?
$0.01 per CV. Ten CVs cost $0.10, and CVs that fail aren't charged. You pay from a prepaid balance with no subscription, monthly minimum, or setup fee.
If monthly tool fees are part of why you're thinking about building your own hiring stack, this cost only moves when you parse. You top up by card through Stripe, with optional automatic top-up. The Developer Console API is billed separately from Curriculo's Starter and Pro plans, and you don't need either one. Billing details are in Pricing and billing.
Is there a free resume parser API?
It's free to start. Every account gets a one-time $5.00 credit, enough to parse 500 CVs at $0.01 each, with no subscription. The parser isn't free forever. After that, parsing draws on your prepaid balance at the same rate.
500 CVs is room to run your own files through the parser and check the JSON against your data model before you top up.
What happens to the CV data?
It depends on the endpoint. A synchronous parse is stateless, and nothing is kept after the response. Async parsing through /parse/async keeps the task, the result, and the files.
The data-handling docs add one caveat for sync calls: a short excerpt may be kept when a model call fails. If you need to tell your own customers where candidate data goes, start with Data handling. Also see the Privacy Policy, the Data Processing Agreement, and the Terms of Service.
From parsing to ranking
The /evaluate/ endpoint scores each CV against a job, at $0.01 per CV. You decide what to do with the score.
If you want the repetitive reading off your team's plate while they keep working the way they already do, parse and evaluate run as two calls inside your own product. The docs also list /translate/ as a next step. Start with AI APIs for ATS builders or the evaluate endpoint.
Resume parser API vs building your own parser
Build your own if parsing is the product you sell. If it's one step inside your product, building means owning three problems: file variety, dates and languages, and maintenance.
File variety. CVs come from different word processors and templates, in one column or two, with tables, sidebars, and contact details tucked into headers. Each new layout is another case your extractor has to handle. The Curriculo API takes PDF and DOCX and returns the same JSON fields for each.
Dates and languages. One role can be written as "2019 to present", "03/2019 to now", or in another language and script entirely. Your parser has to tie each date range to the right role, in whatever language the candidate wrote. The API returns roles with their dates, in the CV's own language and script.
Maintenance. Hiring software gets tedious to maintain once you count the messy cases: empty uploads, password-protected files, oversized documents, runs that never finish. With the API, you don't maintain the parser. Those cases come back as documented errors: 400 for an empty, unreadable or password-protected document, 413 for size limits, and 504 when processing passes 300 seconds.
Build your own ATS experience on Curriculo's API
$5 free credit. No subscription. No ATS login.
Frequently asked questions
Is there a free resume parser API?
Curriculo's parser isn't free forever, but every account starts with a one-time $5.00 credit, enough to parse 500 CVs at $0.01 each, with no subscription.
What file formats does the CV parser API accept?
PDF and DOCX only, up to 10 MB each and up to 10 documents per request, with a 12 MB limit on the request body. Readable scans may be OCR'd. Empty, unreadable or password-protected documents return a 400.
How long does parsing take?
About 40 to 90 seconds per document. Set your client timeout above five minutes, since requests return a 504 after 300 seconds, or use /parse/async for backlogs. Sustained throughput is about 2 to 4 CVs a minute. See Rate limits.
Does the API store resumes?
It depends on the endpoint. A synchronous parse is stateless and nothing is kept after the response, though a short excerpt may be kept when a model call fails. /parse/async keeps the task, the result, and the files. See Data handling.
Can it parse CVs in other languages?
Yes. Fields come back in the CV's own language and script, without translation.
Is a resume parser the same as a CV parser?
Yes. "Resume" is the usual US term and "CV" is used in most other countries. The API accepts both. For background, see resume parsing.
How do I get an API key?
Sign in at console.curriculo.me, open API keys and choose Create API key. The key is shown once, so store it safely.