The job API
All endpoints use your organization API key and support sandbox and production environments.
Production requests require production API access. Each request accesses only jobs in your organization and the selected environment.
List your jobs
CallGET /jobs to retrieve your organization’s jobs, including jobs created outside the API.
By default, only OPEN jobs are returned.
Results are ordered by creation date, newest first, then by Collective job ID in descending order for jobs with the same creation date.
COLLECTIVE_API_KEY to your organization API key. Replace sandbox with production to list production jobs.
When provided, search matches part of the title without regard to case, within the selected statuses.
Use status to select the jobs to include:
Use uppercase values and pass
ALL by itself. Empty or invalid values return 400.
For example, add --data-urlencode 'status=OPEN,PAUSED' to the request above.
The response contains jobs, total, page, and pageSize.
total counts all matching jobs across pages. Increase page until page * pageSize is at least total to retrieve all results.
The default page is 1, and the default page size is 50. See List jobs for parameter limits and response fields.
The list includes expired jobs whose status is still
OPEN. Check isExpired
to hide expired jobs on your careers site. Use status to include paused or
closed jobs. Deleted jobs are always excluded.Job responses
The list returns job summaries with identifiers, status, dates, title, company, budget, contract type, location, work preferences, skills, and language. The get, create, update, and close endpoints return the full job, which also includesdescription, profileWanted, questions, requirePhoneNumber, and notifyByEmailForEveryApplication.
jobUrlis the public URL in the formhttps://www.collective.work/jobs/<language>/<slug>.statusisOPEN,PAUSED, orCLOSED. Expiration does not change a job’s status.isExpiredindicates whether its expiration date has passed.workPreferencesis an array ofREMOTE,HYBRID, orON_SITEvalues in responses. Job creation and update accept a single string.GET /jobreturns the full job for any status, including closed jobs. Deleted jobs return404.DELETE /jobreturns the full job withstatus: "CLOSED"and its closing date inclosedAt.
Pause or resume a job
Sendstatus to Update a job, alone or together with content changes:
- Set
statustoPAUSEDto pause a job, orOPENto resume it. Repeating either request is supported and keeps the original pause date. - Omit
statusto edit a job without changing its status. - Resuming does not extend an expired job. Send
expirationDatewithOPENto set a new expiration date on the job and its applications. - Closed and deleted jobs return
404. A closed job cannot be reopened.
Applications after closing
Get applications and Get application remain available for closed jobs. These reads are scoped to your organization and the selected environment. In the sandbox, they return sample applications attached to your sandbox jobs, including closed jobs.Understanding the job identifiers
Both fields are always present in job summaries, full job responses, and application list responses.
For requests that take an
id, you can pass either the Collective jobId or your internalJobId.
Choose an internalJobId
Use an identifier that is unique in your organization, such as your database ID or a job URL slug. Examples include550e8400-e29b-41d4-a716-446655440000 and javascript-developer-paris-03123.
internalJobId is optional. If you omit it, store the jobId returned by the create endpoint to retrieve, update, or close the job later.
Set the identifier at creation
You can setinternalJobId only when creating a job. Updates cannot change it.
