Expert Hire APIs

Two APIs. Pick the one that matches what you are doing.

Expert Hire publishes two separate APIs. They are different products with different keys, different URLs and different results. Pick one before you read anything else.

Hiring APII am evaluating people I might hireScreen applicants, run AI interviews, score resumes against a role, decide who a recruiter should talk to.ehs_keyshiring-api.experthire.cloud Preparation APII am helping people preparePractice interviews, resume feedback, coding and psychometric assessments for your own users or students.ehp_keysprep-api.experthire.cloud

They are not interchangeable

The same words mean different things in each.

	Hiring	Preparation
The person	A candidate being assessed for a role	A learner practising
The result	A hiring signal you act on	Feedback the learner acts on
Key prefix	`ehs_sk_live_` / `ehs_sk_test_`	`ehp_sk_live_` / `ehp_sk_test_`
Base URL	`hiring-api.experthire.cloud`	`prep-api.experthire.cloud`

A key from one is rejected by the other. That is deliberate: the prefixes are namespaced so an integration cannot quietly point at the wrong product and produce results that look plausible and mean nothing.

Using both? They are independent integrations. Register separately, store the keys separately, and do not share a webhook endpoint between them.

What is the same

Both work the same way once you have picked one:

Your server calls the API with a secret key.
The candidate or learner opens a link, or your page embeds the session.
Your webhook endpoint receives the result, so you are not polling.

Both have a sandbox that costs nothing, and both return a signed webhook you should verify on the raw body.