For HR software vendors
Recruiting features for your HR product, without building the models
HireLayer is the backend behind features your users see under your brand: profiles created from a CV, job requirements drafted from a description, skill tags that stay consistent across customers. Your product keeps the interface, the tenant model and the data.
Why recruiting features stall on HR roadmaps
Customers ask for “AI” in the recruiting module. Behind that request are four separate capabilities, and none of them is your core product.
- 01
Each feature is a different model to build
Reading CVs, interpreting job ads, normalizing skills and comparing profiles are four problems. Solving them in-house competes with payroll, onboarding or performance work.
- 02
Your customers expect your interface
An embedded third-party screen breaks your design system, your permissions model and your support flow.
- 03
Skill data drifts across tenants
“JS”, “Javascript” and “JavaScript developer” end up as three tags. Search and reporting across customers stop being reliable.
- 04
Retention rules differ per customer
Some tenants accept processing and storage by a sub-processor, others do not. The integration has to respect that on every request.
Five features on one integration
Each card is a feature your users would see, the endpoint behind it and the fields you render. Ship one, then add the next on the same API key.
Create a profile from a CV
POST /
api/ v4/ resumes/ parse info_candidatework_experiences[]educations[]Product detailsDraft job requirements
POST /
api/ v4/ jobs/ extract-criteria labelweightrequirementProduct detailsTag skills from free text
POST /
api/ v4/ skills/ normalize skills[].idnamefamiliesProduct detailsExplain a candidate’s fit
POST /
api/ v4/ resumes/ score statusevidenceexplanationProduct detailsOrder a shortlist
POST /
api/ v4/ resumes/ score rankscoreranking_reasonProduct details
Data path for every feature
Your interface
Forms and components you own
Your backend
Tenant rules · API key · retention flag
HireLayer API
One request, structured JSON back
Your database
Employee, candidate and job records
The browser never holds the key:POST/api/v4/…is only called from your server.
A capability layer behind your own endpoints
Your frontend never talks to HireLayer. Your backend adds tenant context, calls the endpoint and stores the result in your own entities.
- Your system
Step 1, your system: A user acts in your product
Uploads a CV, pastes a job description or types a skill, in a form you designed.
- Your system
Step 2, your system: Your backend applies tenant rules
Checks permissions, reads the API key from server config, sends the tenant’s id as HireLayer-Workspace and decides whether to set do_not_store_data for this tenant.
- HireLayer
Step 3, HireLayer API: The relevant API answers
Parsing, criteria extraction, scoring and ranking, searches or skills: each is one JSON or multipart request.
POST /
api/ v4/ … - structured JSON
- Your system
Step 4, your system: Map into your entities
Store fields on your employee, candidate or job objects. Keep the request_id of each parse for support tickets.
- Your system
Step 5, your system: Render in your design system
Show results as editable suggestions, so users confirm before anything is saved.
Every endpoint is documented with request fields, limits and error codes.
Browse the API referenceA “draft requirements” endpoint in your backend
A route handler your job editor calls. The API key stays on your server and the result is saved as a draft the hiring manager edits.
- text · job_id
- The description and your own id: the job is stored under it. An unknown field returns 400.
- label · threshold
- Written in the job’s language: English, French, German, Spanish or Portuguese, and English for any other.
- criterion_id
- crit_1, crit_2… Resume Scorer reads the stored criteria; edit one with PATCH /api/v4/jobs/{job_id}/criteria/{criterion_id}.
// POST /api/jobs/:id/draft-requirements, in your backend
export async function POST(req: Request, { params }: Ctx) {
const tenant = await requireTenant(req) // your auth
const job = await jobs.find(tenant.id, params.id)
const res = await fetch(
'https://hirelayer.co/api/v4/jobs/extract-criteria',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-API-Key': process.env.HIRELAYER_API_KEY!,
'HireLayer-Workspace': tenant.id, // one workspace per customer
},
body: JSON.stringify({
text: job.description,
title: job.title,
job_id: job.id,
}),
}
)
const { criteria } = await res.json()
// Saved as a draft: weights are edited before publishing
await jobs.saveDraftCriteria(tenant.id, job.id, criteria)
return Response.json(criteria)
}{
"job_id": "job-4821",
"stored": true,
"title": "Payroll Manager",
"location": null,
"language": "en",
"criteria": [
{
"criterion_id": "crit_1",
"label": "Multi-entity payroll management",
"type": "experience",
"requirement": "required",
"weight": 3,
"threshold": null,
"source": "extracted"
},
{
"criterion_id": "crit_2",
"label": "HRIS proficiency",
"type": "skill",
"requirement": "preferred",
"weight": 2,
"threshold": null,
"source": "extracted"
}
],
"credits_used": 0
}What changes for your product team
Features, not research projects
Each capability is an HTTP call your backend team can wire in, test and release behind a feature flag.
Your brand from end to end
Users never see a HireLayer screen. Results arrive as JSON you render with your own components.
Retention decided per tenant
Choose request by request whether parsed data may be retained, to match each customer contract.
One unit of cost
Every product draws from a single credit balance: 1 credit per resume parsed or scored, per search or per skills call, and job criteria for free.
The HireLayer APIs behind this workflow
Start with the core APIs, add the others when a feature needs them. All six products share one API key and one credit balance.
- HireLayer Resume Parser
Resume Parsing API
Core to this workflowDocs for HireLayer Resume ParserCreates profiles from a CV, with do_not_store_data available per request.
- HireLayer Job Criteria Extractor
Job Parsing API
Core to this workflowDocs for HireLayer Job Criteria ExtractorDrafts weighted requirements from a job description.
- HireLayer Skills Normalizer
Skills Matching API
Core to this workflowDocs for HireLayer Skills NormalizerPowers skill tagging and clean-up, from one skill to a whole skills section per call.
- HireLayer Resume Scorer
Candidate & Job Matching API
Add when neededDocs for HireLayer Resume ScorerExplains a candidate’s fit for a job, criterion by criterion, and orders candidates with its precise_ranking option when your recruiting module needs it.
HR software & SaaS: frequently asked questions
Can we offer these features under our own brand?
Can our frontend call the API directly?
How do we expose a no-retention option in our tenant settings?
Which language are generated texts written in?
How is usage billed when we serve many customers?
Prototype one feature this sprint
Start with the endpoint behind your most requested feature, then add the others on the same key. The free plan includes 50 credits a month, shared by all six products.
Also built on HireLayer
- ATS platformsParse CVs on upload and show recruiters why a candidate fits.
- Job boards & career sitesPrefill profiles from a CV and explain fit on job pages.
- Sourcing toolsNormalize skills across sources and rank sourced longlists.
Implementation guides
- Resume parser API integration guideSend files from your backend, map the JSON and handle errors.
- Resume parser API pricing per 1,000 CVsCompare price models and calculate your effective cost.
- Greenhouse API guideHarvest v3 auth, pagination, rate limits and resume attachments.
- Bullhorn API guideOAuth, REST login, candidate search, resume files and event polling.
- Ashby API guideAPI key auth, candidate sync, resume downloads and webhooks.
- Lever API guideAPI key auth, opportunities, pagination, resume downloads and webhooks.