Get started
Limits and credits
What each HireLayer product costs, how large a call can be, and which client timeouts to use.
| Product | Endpoint | Credits |
|---|---|---|
| Resume Parser | POST /api/v4/resumes/parse | 1 credit; 0 when the file is already stored |
| Job Criteria Extractor | POST /api/v4/jobs/extract-criteria | Free; 1 credit per stored score evaluated again when a new text replaces a stored job |
| Resume Scorer | POST /api/v4/resumes/score | 1 credit per resume evaluated, +1 per resume file parsed, +1 per call with precise_ranking; 0 for a pair already evaluated or a file already stored; 1 credit per other stored score evaluated again when a stored job comes with a new text or new criteria |
| Talent Pool Search | POST /api/v4/resumes/search | 1 credit per search; 1 credit per stored score evaluated again when a new text replaces a stored job |
| Job Recommendations | POST /api/v4/jobs/search | 1 credit per search, +1 for a resume file |
| Skills Normalizer | POST /api/v4/skills/normalize | 1 credit |
- The six products return
credits_used: what the call cost. - Reads (except
GET /skills, the whole taxonomy, 1 credit, and a ranking read withprecise_ranking=true, 1 credit), stored objects, workspaces, the account and the health check are free. Changing a criterion’s weight, requirement or type re-ranks for free; adding a criterion or changing its label or threshold re-evaluates the job’s stored scores, 1 credit each, and so does a new text or new criteria sent for a stored job already scored, toPOST /jobs/extract-criteria,POST /resumes/scoreorPOST /resumes/search, 1 credit each. - Failed work is not billed, and a call refused for lack of credits processes nothing (
403 insufficient_credits). The Resume Scorer and Talent Pool Search check for the worst case (every stored score of the job counted as evaluated again) and bill only what they do. - Plans: Free: 50 credits/month · Starter: 500 credits/month · Scale: 2,000 credits/month; Enterprise on request. Monthly credits renew each billing month; credit packs, bought once from the dashboard, stay until used and are spent after them. Prices are on the pricing page.
GET /api/v4/accountgives the balance.
| Input | Limit |
|---|---|
| A file (resume or job) | 4.5 MB · 50 MB of files per call |
| A job file as PDF | 50 pages |
| A job or resume text | 50,000 characters |
| A parsed resume sent as JSON | 1 MB |
| Resumes per scoring call | 100; synchronous up to 10 files and 50 resumes |
| Criteria per job | 20 |
| Skills text | 5,000 characters |
| Talent Pool Search | Up to 500 resumes per search |
| Job Recommendations | Up to 100 jobs per search |
| List pages | Up to 100 items, with next_cursor |
- Resume Parser: about 25 to 35 seconds, scans longer; set a client timeout of 150 seconds.
- Resume Scorer: about a minute for 50 resumes, plus the parse of any file; 150 seconds. Larger calls answer
202, and so does a call with storage whose evaluations still run after about 100 seconds: see Webhooks. - Other calls answer in a few seconds.
No per-second rate limit is enforced, but capacity is shared: too many files parsed at once answer 429 rate_limited with Retry-After. Start with a few concurrent requests, increase gradually, and back off on 502 and 503. For bulk imports, contact us first.