How to manage Zeus AI API
Last updated September 17, 2026
The API authentication section (located under " Zeus AI > Configurations > API ") centralizes all secret tokens and security credentials required to connect external channels, backend services, or custom software directly to the Zeus AI engine inside Atlas.
Because Zeus AI generate responses based on your configured data sources, these credentials act as a secure gateway, ensuring that every request sent to or received from Zeus AI is encrypted, verified, and restricted to authorized systems.
Key features
- API Token (From external systems to Atlas Zeus AI): Users can take the primary password that grants external applications or custom frontends permission to send requests directly to Zeus AI inside Atlas. When Zeus AI sends a message prompt, it presents this token to authenticate the request.
- Webhook Secret (From Atlas Zeus AI to external systems): A digital signature key used to verify automated event notifications sent from Zeus AI out to your external servers (e.g., notifying your backend when Zeus AI finishes generating a response). It allows your system to confirm that incoming data genuinely originated from Zeus AI in Atlas and was not forged.
- User Signing Secret (End-User Identity & Integrity Guard): A secret cryptographic key used by your backend server to generate a secure digital signature (hash) for end-user data (such as user_id or email) before passing it to Zeus AI. When Zeus AI receives a customer request, it uses this secret to verify the signature, ensuring that the user identity has not been tampered with or forged on the client side, preventing users from spoofing another account or accessing unauthorized data sources.
How to retrieve or copy your API authentication token, webhook secret, or user signing secret credentials
- Navigate to " Zeus AI > Configurations > API ".
- Locate the required credential (API token, Webhook secret, or User signing secret).
- Select the eye icon to display the key, or use the copy icon to copy it directly to your clipboard.
Authenticating requests to Zeus AI
- Copy your API Token.
- Pass the token in the HTTP request headers from your external application: (e.g.: Header: Authorization: Bearer <YOUR_API_TOKEN>)
How to manage compromised credentials
If a credential is compromised or leaked, contact your system administrator or support team immediately to request a backend key rotation, as manual revocation is not available in the UI.
FAQs & Troubleshooting
Can I revoke or regenerate my Zeus AI API Token or Secrets?
No. The interface only allows viewing and copying credentials. If a key is leaked or needs to be rotated, you must contact support or your system administrator to issue a new set of keys.
Why is the user signing secret needed?
The User signing secret ensures that when end-user profile details are passed into a session, they are cryptographically signed by your server to prevent malicious users from altering customer IDs or spoofing another user's account in their browser.
What happens if a Webhook signature verification fails?
If an incoming event payload sent by Zeus AI does not match the signature derived from your Webhook secret, your receiving server should reject the payload (returning a 401 or 403 HTTP status) to block unverified requests.
Where can I find the full technical endpoints and request schemas?
The API documentation provides a developer reference for Zeus AI.