Skip to main content
POST
Create Candidate
To create an candidate in ATS, you first need to fetch the request body structure that ATS expects. This structure varies based on the ATS provider (e.g., Greenhouse, Teamtailor, BambooHR). The request body consists of three parts:
  • Model Keys: Standard attributes required for all candidate.
  • Additional Attributes: Specific fields required by the chosen ATS.
  • Custom Fields: Extra metadata for specific implementations.
Note: Some attributes may have allowed_values, meaning only specific values are permitted based on the customer’s ATS configuration. Ensure you check for these constraints before submitting the request.

Step 1: Fetch the Required Request Body

Before calling the Create Candidate API, you need to get the request structure using the Meta Create Candidate API.

Step 2: Create an Candidate

Once you have the request body structure, use the Create Candidate API to send the request.

Authorizations

Authorization
string
header
default:<BINDBEE_API_KEY>
required

Your Bindbee API key, sent as Authorization: Bearer <BINDBEE_API_KEY>. Required on every request.

X-Connector-Token
string
header
default:<CONNECTOR_TOKEN>
required

The connector token for one customer's connection. This is not your Bindbee API key. Required on requests that read or write a single customer's data.

Body

application/json
data
PostCandidate · object
required
remote_user_id
string | null

The remote user's id

Example:

"018b4bfb-5ece-70b1-ad5e-862a9433aa65"

job_requisition_id
string | null

The job requisition id in external ATS

Example:

"R-00007"

Response

Successful Response