Skip to content

Atlast Public Jobs API

The Atlast Public Jobs API lets your systems read the jobs your organisation has published on Atlast, and receive webhooks the moment a job is published, updated, unpublished, or deleted.

It’s a small, read-only REST API designed for one job: keeping an external system (your own careers site, a job board, an internal dashboard) in sync with the jobs you manage in Atlast.

Section titled “The recommended pattern — webhooks, then re-fetch”

Atlast is built to be used event-driven, not polled. The whole integration is one loop:

  1. Atlast notifies you. When a job changes, Atlast sends a small webhook to your endpoint saying what changed and where to fetch it — not the full job.
  2. You fetch the change. Your integration calls the Jobs API for that one job and gets its full, current detail.
  3. You store it. Upsert the result into your own system.
The webhook and re-fetch loop Atlast sends a thin webhook when a job changes. Your integration verifies it, then calls GET /jobs/{publicId} on the Atlast Jobs API to load the full, current job, and upserts it into your data store. Atlast events + Jobs API Your integration verify · enqueue Your data store Webhook — job changed (thin payload) GET /jobs/{publicId} Full, current job JSON Upsert

Because you always reconcile against the live API — the source of truth — this stays correct even when events arrive out of order or more than once, and it costs a single request per change instead of constant polling. The full mechanics are in the re-fetch pattern.

  • Subscribe to webhooks — get notified on job.published, job.updated, job.unpublished, and job.deleted, then re-fetch the affected job. This is how you stay in sync.
  • Fetch a single job — full detail by its public identifier (the call you make when a webhook arrives).
  • List published jobs — paginated summaries, for the initial backfill and periodic reconciliation.

All endpoints live under:

https://api.atlasthq.com/api/public/v1
  1. Create an API key in the Atlast Portal (Settings → Integrations).
  2. Configure your webhook endpoint so Atlast can push changes to you, and verify its signatures.
  3. Backfill once by paging the list endpoint, then let webhooks keep you current.