The Job Posting API can be used for different use cases, however, the most popular one is the multi-posting integration. In addition, it is also possible to set it up for individual recruiters who prefer to post their jobs via an API instead of accessing the job board directly or using an XML importer.
Multi-posting allows recruiters to enter job details in one tool and then have them pushed to multiple job boards at the same time, without needing accounts on each job board or manually entering them on multiple job boards. Additionally, the applications from each job board are also fed back to the multi-posting tool, meaning that recruiters can manage their whole hiring process within one tool.
As multi-posters themselves also have some setup effort on their side when integrating with a new job board, we recommend planning for a longer lead time for the solution implementation.
The Job Posting API module needs to be set up specifically for your project. Please reach out to your main contact at Jobiqo to discuss details and pricing.
What needs to be set up in order to use the Job Posting API?
Once the module has been enabled and configured, specific configurations need to be completed for each individual use case (e.g. for each multi-poster that should be supported).
For each new source of job postings (e.g. multi-poster) you need an API key. Additionally, each recruiter that should be able to post through the various sources also needs a specific API key.
Upon successful completion of the main setup, your main contact at Jobiqo can support you in this setup and show you how you can easily do this on your own for subsequent new use cases or new recruiters.
Which requests are supported?
The Job Posting API enables you to add, update and delete jobs via API calls. The API supports 2 data formats for the data input and output (JSON and XML).
The following requests are supported:
| Request | API endpoint | HTTP Method |
| Create a new job | /api/v1/job/create | POST |
| Update an existing job | /api/v1/job/{job_id} | PATCH |
| View an existing job | /api/v1/job/{job_id} | GET |
| View the recruiter's job list | /api/v1/job-list | GET |
| Unpublish an existing job | /api/v1/job/{job_id} | DELETE |
| View employment types | /api/v1/taxonomy-vocabulary/employment_type | GET |
| View fields of study | /api/v1/taxonomy-vocabulary/fields_of_study | GET |
| View occupational fields | /api/v1/taxonomy-vocabulary/occupational_fields | GET |
| View remote options | /api/v1/taxonomy-vocabulary/remove_options | GET |
| View possible years of experience | /api/v1/taxonomy-vocabulary/skills | GET |
| View required languages | /api/v1/taxonomy-vocabulary/languages | GET |
| View salary range | /api/v1/taxonomy-vocabulary/salary_range | GET |
| View locations | /api/taxonomy-vocabulary/geography | GET |
When will a job that has been posted via the API be available on the job board?
Once a job was successfully posted via the API, it will immediately be available on the job board. The only exception is if a specific publication date in the future was specified within the API request.
Please note that the "Needs review" workflow is currently not available in combination with the Job Posting API.
Do recruiters need credits or an active flat rate to post a job?
Yes, a credit / flat rate check will be performed during the job posting process via the API. If the recruiter does not have sufficient credits or no active flat rate, an error message will be returned via the API.
Please note that even if a job has a publication date in the future, the credit is deducted immediately and (in case this is active on your job board) a job slot is immediately blocked.
How long will a job be online that has been posted via the API?
Generally, job postings via the API are handled like any other job, so the job will be online for the number of days defined for the standard job duration on the job board.
It is possible to define an earlier expiration date via the API request in case a job should go offline earlier.