Authentication

Every request to the Jobs API must be authenticated with an API key that belongs to your organisation. The key determines which organisation’s jobs you can read — you never pass an organisation ID yourself.

Creating a key

In the Atlast Portal, go to Settings → Integrations → API keys and create a key.

The key is shown once

For security, the full key value is displayed only at creation time. Copy it immediately and store it in your secrets manager. If you lose it, revoke it and create a new one — Atlast cannot show it to you again.

Using a key

Pass the key on every request, using either header:

Recommended — Authorization header

curl https://api.atlasthq.com/api/public/v1/jobs \
  -H "Authorization: Bearer atlk_live_8f3c2a1b9d4e5f60a7b8c9d0e1f2a3b4"

Alternative — x-api-key header

curl https://api.atlasthq.com/api/public/v1/jobs \
  -H "x-api-key: atlk_live_8f3c2a1b9d4e5f60a7b8c9d0e1f2a3b4"

Both are equivalent. Use whichever your HTTP client makes easiest.

Revoking a key

Revoke a key from the same API keys screen. Revocation is immediate — the next request made with that key returns 401 Unauthorized. Create a replacement key first if you’re rotating, to avoid downtime.

Keeping keys safe

• Never embed a key in client-side code, a mobile app, or a public repo — anyone with the key can read your published jobs.
• Use a separate key per integration so you can revoke one without breaking the others.
• Use a separate key per environment — see Environments.

What can go wrong

Status	Meaning
401 Unauthorized	The key is missing, malformed, or has been revoked.
403 Forbidden	The key is valid, but your plan doesn’t include the public API.

See Errors & rate limits for the full list.