Skip to content

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.

A white-label HR product showing a job requirements editor. Four requirements drafted from the job description have weights and a must-have toggle. A server log shows the product's backend calling the HireLayer criteria extraction endpoint and saving the result as a draft.

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.

  1. 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.

  2. 02

    Your customers expect your interface

    An embedded third-party screen breaks your design system, your permissions model and your support flow.

  3. 03

    Skill data drifts across tenants

    “JS”, “Javascript” and “JavaScript developer” end up as three tags. Search and reporting across customers stop being reliable.

  4. 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 details
  • Draft job requirements

    POST /api/v4/jobs/extract-criteria

    labelweightrequirement
    Product details
  • Tag skills from free text

    POST /api/v4/skills/normalize

    skills[].idnamefamilies
    Product details
  • Explain a candidate’s fit

    POST /api/v4/resumes/score

    statusevidenceexplanation
    Product details
  • Order a shortlist

    POST /api/v4/resumes/score

    rankscoreranking_reason
    Product details

Data path for every feature

  1. Your interface

    Forms and components you own

  2. Your backend

    Tenant rules · API key · retention flag

  3. HireLayer API

    One request, structured JSON back

  4. 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.

  1. 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.

  2. 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.

  3. 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
  4. 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.

  5. 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 reference

A “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}.
Request · TypeScript/api/v4/jobs/extract-criteria
// 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)
}
Response · abridged
{
  "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.

HR software & SaaS: frequently asked questions

Can we offer these features under our own brand?

Yes. HireLayer is API-only: there is no widget or HireLayer screen in your product. Your backend calls the API and your interface renders the result.

Can our frontend call the API directly?

Keep the API key on your server. Expose your own endpoint to the frontend, apply tenant permissions there, then call HireLayer.

How do we expose a no-retention option in our tenant settings?

Store the choice in each tenant’s configuration and have your backend add do_not_store_data, set to true, to that tenant’s parsing calls. Your product still receives the parsed result and renders it under your brand as usual.

Which language are generated texts written in?

CV fields keep the values found in the document. Job criteria, summaries and explanations are written in the job’s language (English, French, German, Spanish or Portuguese; English for any other) unless you set language. Plan your UI copy around them, or translate on your side.

How is usage billed when we serve many customers?

All calls draw from one credit balance: 1 credit per resume parsed, per resume scored, per search and per skills call, while job criteria are free. Log each call with the tenant on your side to allocate usage per customer.

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.