Skip to main content

JobBoardly API

This guide explains how to manage jobs programmatically using the JobBoardly API.

Joaquin Cahiza avatar
Written by Joaquin Cahiza
Updated today


JobBoardly API — Jobs Endpoints

This guide explains how to manage jobs programmatically using the JobBoardly API.

You can use these endpoints to:

  • Sync jobs from external systems

  • Create, update, publish, or delete jobs

  • Manage jobs in bulk

  • Build custom workflows and integrations


1. Authentication

Before making any requests, you must authenticate using your API credentials.

In the API Docs:

  1. Open api.jobboardly.com/api-docs

  2. Click Authorize

  3. Paste your API token

  4. Click Authorize

Once authorized, all requests made via Try it out will include your credentials automatically.


2. Get current board

GET — Get current board

This endpoint returns information about the current job board associated with your API token.

Use this to:

  • Verify authentication

  • Fetch board metadata (ID, name, settings)

Typical use case: testing that your API connection works correctly.


3. List jobs

GET — List jobs

Returns a list of jobs from your job board.

Common use cases:

  • Sync jobs into another platform

  • Build custom dashboards

  • Export jobs for reporting

This endpoint usually supports:

  • Pagination

  • Filtering by status (draft, published, expired, deleted)

  • Sorting

Always check the Parameters section in the docs for available filters.


4. Create a job

POST — Create job

Creates a new job in your job board.

Important notes:

  • Newly created jobs are usually created as draft

  • A job must be published before it becomes visible publicly

Typical workflow:

  1. Create job

  2. Publish job


5. Show job

GET — Show job

Returns a single job by ID.

Use this to:

  • Fetch full job details

  • Verify job data after creation or update

  • Debug sync issues


6. Update job

PATCH — Update job

Updates an existing job.

You can modify:

  • Title

  • Description

  • Location

  • Salary

  • Metadata

Only the fields sent in the request body will be updated.


7. Delete job

DELETE — Delete job

Deletes a job from the board.

Important:

  • Deleted jobs can often be restored (see Restore job)

  • Use this instead of permanent deletion when syncing


8. Publish & unpublish jobs

Publish job

POST — Publish job

Makes a job publicly visible on your job board.

Unpublish job

POST — Unpublish job

Removes a job from public view without deleting it.

Common use case:

  • Temporarily hide jobs without losing data


9. Restore job

PATCH — Restore job

Restores a previously deleted job.

Useful when:

  • A job was deleted by mistake

  • Re-syncing historical data


10. Job counts by state

GET — Job counts by state

Returns job counts grouped by status, such as:

  • Draft

  • Published

  • Expired

  • Deleted

Perfect for:

  • Admin dashboards

  • Monitoring job board health

  • Automation logic


11. Bulk job actions

JobBoardly supports bulk operations to manage multiple jobs efficiently.

Bulk move to draft

POST — Bulk move to draft

Moves multiple jobs back to draft status.

Bulk publish

POST — Bulk publish

Publishes multiple jobs at once.

Bulk expire

POST — Bulk expire

Expires multiple jobs.

Bulk delete

POST — Bulk delete

Deletes multiple jobs in one request.

Bulk actions are ideal for:

  • Large imports

  • Job feeds

  • Periodic cleanup


12. Recommended workflow example

A common API workflow looks like this:

  1. List jobs → check existing jobs

  2. Create job → add new positions

  3. Update job → sync changes

  4. Publish job → make jobs live

  5. Bulk expire/delete → clean up old jobs


13. Best practices

  • Always test endpoints using Try it out first

  • Create jobs as draft, then publish explicitly

  • Use bulk endpoints for large imports

  • Handle error responses (401, 403, 422) gracefully

  • Avoid hardcoding API tokens in frontend apps


Did this answer your question?