Hiring API
Assess candidates for a role and get a score you can act on.
The Hiring API screens candidates. You register a role, send us a candidate, and get back a scored assessment.
If you are helping people practise rather than deciding who to hire, you want the Preparation API instead.
What you can build
- Screen everyone who applies. Create an assessment per applicant, send each a link, and collect scored results as they finish.
- Score a resume against a role before a human reads it.
- Put an interview inside your own product, so the candidate never leaves it.
Two kinds of assessment
| Type | What happens | Good for |
|---|---|---|
resume_screen | We score the candidate's resume against the role | Cutting a large applicant pool down |
ai_interview | An AI interviewer conducts a call and scores it | Deciding who a recruiter should speak to |
You do not manage interview rounds. You give us a role and a type, and we build the rest.
How an integration fits together
- Register a role once, with
POST /v1/jobs. - Create an assessment per candidate, with
POST /v1/assessments. - Send them in, either with a link from
POST /v1/assessments/{id}/launch-linkor by embedding the session in your own page. - Optionally set a time with
POST /v1/assessments/{id}/schedule. - Receive the result on your webhook endpoint.
Before you start
- Keys start with
ehs_. Get one from Settings → Developers in your Expert Hire dashboard. You will see the secret once. - Start with a test key. It costs nothing, records nothing, and its assessments never reach your recruiters' pipeline.
- Base URL is
https://api.experthire.cloud.
A ehp_ key from the Preparation API will not work here, and vice versa. The
prefixes are namespaced so a misconfigured integration fails loudly instead of
producing results that look right and mean nothing.
Next: the quickstart runs one assessment end to end.