Skip to main content
Everything under https://api.bindbee.dev/api/ats/v1/. Sixteen models covering candidates, the jobs they apply to, and the process in between. A connector token is category-scoped: an HRIS token used on an ATS path returns 403 even though the credentials are valid.

​
The models

Candidate and Application are not the same thing. A candidate is a person and exists once; an application is one candidate’s pursuit of one job. Someone applying to three roles is one candidate and three applications - see ATS models.
EEOC holds race, gender, veteran_status and disability_status, collected for compliance reporting and legally restricted in how it may be used. Most applications should exclude it from scope entirely - see Exclude EEOC Data.

​
This is the write-heavy category

Fifteen of the sixteen models accept creates - candidates, applications, jobs, interviews, scorecards, offers and the rest. That is a far larger write surface than HRIS, where four models accept writes. Only Create Candidate has a Meta endpoint (GET /api/ats/v1/candidates/create/meta). For the others the request shape comes from the reference page, and the per-integration variation a schema would have told you has to be found by attempting the write - see Check write support.

​
Where to start

Writing to an ATS

Fetch the request schema before you write - it varies by connector.

ATS models

What each model holds and why they are separate.