Integrations & operations
- Written for
- ＋ Written for
- Deprecated
- ＋ Deprecated
- Applies to
- ＋ Applies to
Integrations & operations
Atlas doesn't live in isolation. This section covers the machinery that connects it to the rest of your stack and lets you run it day to day: events pushed to your backend, tokens shaped for third-party services, the keys your servers authenticate with, and the numbers that tell you how it's being used.
What's here
Topic | What it's for | Page |
|---|---|---|
Webhooks | React to events ( | |
JWT templates | Mint tokens with custom claims for third-party services | |
API keys & tokens | Authenticate your backend, scoped to exactly what it needs | |
Usage & analytics | See sign-ins, sign-ups and active users over time |
Two directions of integration
Atlas → you. Webhooks push events to your backend so you can provision resources, sync a mirror table, or kick off email. The audit log is the pull-based counterpart.
You → Atlas. Your backend calls the Backend API with a secret key to manage users, organizations, roles and more.
Next
Start with events → Webhooks.