How to manage Zeus AI API
Last updated October 22, 2026
Overview
The API section, in "Zeus AI > Configurations > API" , holds all the secret tokens and security credentials you need to connect external channels, backend services or custom software directly to Zeus AI in Atlas. Because Zeus AI generates responses from your configured data sources, these credentials act as a secure gateway: every request sent to or received from Zeus AI is encrypted, verified and limited to authorized systems.
Key Features
- API Token (from external systems to Zeus AI): The main credential that lets external applications or custom frontends send requests to Zeus AI in Atlas. Each request presents this token to authenticate.
- Webhook Secret (from Zeus AI to external systems): A signature key that verifies the event notifications Zeus AI sends to your servers, for example when Zeus AI finishes generating a response. Your system uses it to confirm the data came from Zeus AI and wasn't forged.
- User Signing Secret (end-user identity): A secret key your backend uses to sign end-user data (such as user_id or email) before passing it to Zeus AI. Zeus AI checks the signature, so users can't tamper with their identity, impersonate another account or access unauthorized data.
How to view or copy your credentials
- Go to "Zeus AI > Configurations > API" .
- Find the credential: API token, Webhook secret or User signing secret.
- Click the eye icon to show it, or the copy icon to copy it to your clipboard.
How to authenticate requests to Zeus AI
- Copy your API Token.
- Send it in the HTTP request headers from your external application, for example
Authorization: Bearer <YOUR_API_TOKEN>.
For endpoints and request schemas, read the API documentation (https://atlas-a61958e8.mintlify.app/).
What to do if a credential is compromised
Contact your system administrator or support team immediately to request a key rotation. Credentials can't be revoked manually in the interface.
FAQs & Troubleshooting
Can I revoke or regenerate my API Token or secrets?
No. You can only view and copy credentials. To rotate a leaked key, contact support or your system administrator.
Why do I need the User signing secret?
It makes sure end-user details passed into a session are signed by your server, so malicious users can't change customer IDs or impersonate another user in their browser.
What happens if a webhook signature verification fails?
If an event sent by Zeus AI doesn't match the signature from your Webhook secret, your server should reject it (for example with a 401 or 403 status) to block unverified requests.