Create Job
Creates a Job object with the given values.
POST
Create Job
This endpoint creates a Job in the connected ATS via Bindbee’s unified Job model.
How to get
Provider-specific behavior
Different ATS providers can have slightly different requirements and behaviors when creating jobs. Use the accordions below to see details for each provider.Greenhouse
Greenhouse
When the underlying ATS is Greenhouse, a job can be created using a payload like:
Required fields
For Greenhouse, the following fields are required when creating a job through Bindbee:- template_id
- remote_user_id
- openings
remote_user_id, departments, offices) should be the Bindbee model IDs returned from the respective unified endpoints, not raw Greenhouse IDs.How to get template_id
- Fetch jobs from the Greenhouse connector using the Bindbee Jobs list endpoint.
- In the
raw_dataof each job, look for entries whereis_templateistrue. - Use either the
idorremote_idfrom that record as thetemplate_idwhen creating a job.
Greenhouse-specific notes
- Single department only: Greenhouse allows only one department per job. Even though the Bindbee model accepts an array in
departments, you should send at most one department ID for Greenhouse. - Multiple offices allowed: You can associate multiple offices with a job by passing multiple Bindbee office IDs in the
officesarray. - Use unified IDs: Always use IDs from Bindbee’s unified models (e.g., Departments, Offices, Remote Users) so that the same payload structure works consistently across ATS providers.
Authorizations
Body
application/json
Response
Successful Response