CandidateZip pricing: plans, credits and per-parse cost
Published
CandidateZip pricing, as of September 2026, is four published monthly plans, each bundling parsing credits with a lower per-credit rate as you go up: Growth at $30/month for 300 credits, Premium at $150/month for 2,000, Platinum at $400/month for 6,500, and Diamond at $750/month for 15,000. Annual billing is ten months for twelve — $300, $1,500, $4,000 and $7,500 a year. One credit parses one resume or one job description, and once a plan's credits are used the overage rate is 8 cents a credit on Growth, 6 on Premium, 5 on Platinum and 4 on Diamond. There is a 7-day trial that asks for no credit card, and the pricing page states a 14-day money-back guarantee on every tier.
That is the whole published table, which already makes CandidateZip unusual in this category — most resume parsing vendors quote. This article is for the person who searched candidatezip pricing because they are sizing a build: what the credit actually buys, where the effective per-parse cost lands at real volumes, who should buy CandidateZip anyway, and where a plain per-parse API is cheaper.
We build ResumeJSON, a per-parse resume parsing API, so read this as written by an interested party. Every figure below about CandidateZip was read from CandidateZip's own pages in September 2026; their pages are theirs to change, so check anything you are about to pay for.
What CandidateZip pricing includes
| Plan | Monthly | Annual | Credits included | Rate past the quota |
|---|---|---|---|---|
| Growth | $30 | $300 | 300 | $0.08 a credit |
| Premium | $150 | $1,500 | 2,000 | $0.06 a credit |
| Platinum | $400 | $4,000 | 6,500 | $0.05 a credit |
| Diamond | $750 | $7,500 | 15,000 | $0.04 a credit |
Every tier lists the same core capability — parse resumes, parse jobs, email support, automatic updates, knowledge base access, the money-back guarantee — with phone support added from Premium upward. The differences between plans are volume and the overage rate, not features, which is a good sign when you are budgeting: you are not being upsold a capability, you are buying a block of parses.
The unit is a credit, and a credit is one document either way. CandidateZip's pricing page states it plainly: "1 Parsing Credit = 1 JD or 1 Resume Parsed". If you parse job descriptions as well as CVs, both draw on the same pool, so size the plan off your combined document count rather than your candidate count.
The effective per-parse cost
The headline rate on a plan is not what you pay per parse unless you use every credit. Divide the monthly fee by the credits actually consumed:
| If you parse | On the smallest plan that covers it | Effective cost per parse |
|---|---|---|
| 100 a month | Growth, $30 | $0.30 |
| 300 a month | Growth, $30 | $0.10 |
| 1,000 a month | Premium, $150 | $0.15 |
| 2,000 a month | Premium, $150 | $0.075 |
| 6,500 a month | Platinum, $400 | $0.062 |
| 15,000 a month | Diamond, $750 | $0.05 |
The pattern is the one every bundled-credit product has: you are efficient at the top of a tier and expensive at the bottom of the next one. A team parsing 400 documents a month either pays Growth plus 100 credits of overage at 8 cents ($38, or $0.095 a parse) or jumps to Premium at $150 and pays $0.375 a parse for what they use. Neither is wrong; both are worth knowing before the renewal.
Who should buy CandidateZip
Plenty of people, and it would be dishonest to pretend otherwise. CandidateZip is not really sold as a parsing API — it is sold as a recruiting workflow product, and its own home page leads with automation rather than with endpoints:
Automate your hiring workflows and find the perfect fit with our innovative tools
Concretely, what it does that a parsing API does not:
- Bulk parsing from a ZIP file — a thousand CVs into one structured table, with no code at all.
- Parsing straight from an inbox, so applications that arrive by email become rows without anyone downloading an attachment.
- Zapier, Power Automate and Workato integrations — CandidateZip's home page cites 2,000+ apps via Zapier and 1,000+ enterprise apps via the other two. This is the real product for most of its buyers: resumes land in an ATS or a spreadsheet without an engineer.
- Job-description parsing and job-to-candidate matching, which a plain CV parser does not attempt.
- Breadth of extraction, advertised as 140+ fields, 30+ languages and 37+ countries supported.
If you are a recruiter or a recruitment-operations lead, and the outcome you want is "resumes from these three sources appear in our ATS every morning", CandidateZip sells you that outcome directly and you should stay with it. A parsing API sells you a JSON document and leaves the rest to a developer you would then have to find.
One thing to check first if you came looking for an API specifically: CandidateZip's API Integration page frames API access as a partner programme you apply to — "Join CandidateZip's Resume/Job Parser API Integration Program", with an Apply Now for API Access button — rather than as a key you get when you subscribe. That is a sales conversation, not a signup, so budget the time for it.
When a per-parse API costs less
The other reader here is the developer building a job board, an ATS or a matching tool, who wants an HTTP endpoint and a typed response, and for whom the workflow layer is weight they will not use.
| CandidateZip | ResumeJSON | |
|---|---|---|
| Shape of the product | Hiring-workflow automation (ZIP, email, Zapier, ATS sync) | One HTTP endpoint that returns typed JSON |
| How you start | Sign-up for the app; API access is an application | Subscribe on RapidAPI, or parse in the browser with no signup |
| Entry price | $30/month for 300 credits | $0 — 100 parses a month on the free tier, a hard cap |
| Pay-as-you-go | Overage on a paid plan, 4–8 cents a credit | $0.05 a parse, no monthly fee |
| Mid volume | $150/month for 2,000 credits | $29/month for 1,000, then $0.045; $99/month for 5,000, then $0.018 |
| Job-description parsing | Yes, same credit pool | No — resumes only |
| Speed published | 300 ms average parse, per its home page | Median 2.2 s, measured against the live endpoint, with an X-Parse-Ms header on every response |
The cheapest honest comparison is at the bottom and at the top. Below a few hundred documents a month a free tier capped at 100 parses and a 5-cent pay-per-use plan will cost you less than $30 a month, because there is no monthly fee to clear. Above a few thousand, the Mega plan's $99 for 5,000 works out at $0.0198 a parse against Platinum's $0.062 — but you are comparing a resume parser with a workflow suite, and if you need the ZIP importer and the ATS sync, the suite is doing work you would otherwise build.
Where CandidateZip is straightforwardly the better answer: job descriptions, no-code integrations, and bulk imports by a non-developer. Where a per-parse API is: you already have the application, you want fields back in-process, and you would rather not pay a monthly floor for automation you are not going to use.
What the fields look like either way
The reason to care about the shape of the output, and not only the price, is that a parser billing you per document can still cost you a week if the dates come back as prose. Ours returns start_date as YYYY-MM or YYYY, never "Summer 2019", sets is_current: true on a role with no end date, and returns null for anything the CV does not state rather than guessing it. If you are evaluating any parser, including CandidateZip, ask for a sample response on your own worst CV before you commit to a plan — the demo file is never the hard one.
There is more on the field-by-field trade-offs in our CV parser API comparison, and on the quote-only enterprise end of the market in Textkernel pricing and DaXtra pricing.
The short version
- CandidateZip publishes real prices, which most of this category does not: $30, $150, $400 and $750 a month for 300, 2,000, 6,500 and 15,000 credits, ten months for twelve on annual billing, and 4–8 cents a credit past the quota.
- A credit is one resume or one job description, so size on total documents.
- Buy it if the value is the workflow — ZIP and email intake, Zapier, ATS sync, JD parsing — and you would rather not write code. Note that API access is an application, not a subscription setting.
- Buy a per-parse API if you are a developer who wants typed JSON from one endpoint, and especially if your volume is low enough that a monthly floor dominates the bill. You can parse a CV free, without signing up, and compare the output yourself before anything is billed.