What is it
Collective provides a platform where anyone can post jobs. The goal of this API is to allow the posting of jobs automatically for platforms that have jobs and want to remove the redundant task of posting jobs manually.The job API
The job API has 4 endpoints:- Getting a job (posted on the Collective platform)
- Creating a job
- Updating a job
- Deleting a job
Understanding the job identifiers
How it works
To help you better track the job posted on the platform, the job API provides a field calledinternalJobId.
This field is a unique string identifier that you can pass when creating a job. It will be indexed
on our side and you can use it to retrieve the job later on.
This is done to prevent you from having to store the job id we create on our side if you already have
an id in your database for it.
All the methods mutating jobs take an id as input, that can be either the generated jobId or the internalJobId
given by you when creating the job.
What is a good internalJobId ?
This is up to you to decide but it should be unique, meaning no 2 jobs from you should have the same internalJobId.
Generally, the best is either the id in your database or the url slug of the job.
Database id examples:
cjn0m98v90000s8k80vjg9s9p550e8400-e29b-41d4-a716-446655440000
javascript-developer-paris-03123e34tgb-product-manager-remote
I don’t have an internalJobId
No worries, it’s not necessary. You can just use our generatedjobId. We return it after the creation
of jobs, so you will just have to store it somehwere if you want to get or update the job.
internalJobId are just provided to ease integration, but are not a requirement.