Environments

If you run more than one environment (for example, a staging system and a production system), keep them cleanly separated.

One key per environment

Create a separate API key for each environment in the Atlast Portal. This lets you:

• Revoke or rotate a staging key without touching production.
• Tell traffic apart — each key has its own rate limit.
• Store each key in that environment’s own secrets manager.

staging

ATLAST_API_KEY=atlk_live_5e4d3c2b1a09f8e7d6c5b4a39281706f

production

ATLAST_API_KEY=atlk_live_8f3c2a1b9d4e5f60a7b8c9d0e1f2a3b4

The base URL is the same for every environment:

https://api.atlasthq.com/api/public/v1

One webhook per organisation

Atlast supports a single webhook endpoint per organisation. If you need to point webhooks at a different environment (say, you’re cutting over from staging to production):

1. Update the webhook URL in Settings → Integrations → Webhook.
2. Reconcile after re-pointing. Any events that fired while the old endpoint was active won’t be replayed to the new one. Immediately after switching, page through the list endpoint and upsert every published job so the new environment starts from a complete, correct baseline.

Reconcile, then rely on webhooks

A full list-and-upsert on cutover (and as an occasional safety net) guarantees you’re in sync even if a webhook was missed. After that, webhooks keep you current.

Signing secrets

Each time you generate or rotate the webhook signing secret, update the secret in the environment that receives the webhooks. Keep staging and production secrets distinct.