To call the Ejento AI APIs from your own code, you need three things: your organization's Server URL, an Authorization Token, and an API key (also called a subscription key). This guide shows where to find the first two, how to create a key with exactly the permissions it needs, and how to change or revoke a key later.Why create separate API keys?#
Least privilege. Give each integration only the access it needs. A reporting script can use a Read Only key, while a sync job can get write access to just the categories it touches.
Easy to retire. If an integration is replaced or a key may have leaked, revoke that one key without affecting anything else.
Clear ownership. The key list shows who created each key, when, its permission, and its status.
Use cases#
Read-only dashboard: A support dashboard reads chat logs every night. Create a key called "Support Dashboard" with Restricted permission and Read access to Chat Logs only. The dashboard reads what it needs and can't change anything, and you revoke the key when the dashboard is retired.Sync job: A job that uploads documents gets Write access to Corpora only, so a bug in it can't touch your assistants or users.Leaked key: If a key may have been exposed, revoke just that key. Integrations that use other keys keep working.Never share your API key or authorization token, and never expose them in a browser or other client-side code.
Find your Server URL and Authorization Token#
1. Open Organization settings#
At the bottom of the sidebar, click your name, then click Organization settings.2. Open API Keys#
In the Organization Settings list, click API Keys. This page lists your organization's keys with their name, owner, creation date, permission, and status.3. Copy your Server URL and Authorization Token#
Use the copy icons next to Server URL and Authorization Token. Use the Server URL as the base URL for your API requests, and send the Authorization Token in the request header as a Bearer token.From here you can also open the API Documentation and check Rate Limits & Quotas. To see recent API activity, click Show Logs at the top of the page.
Create a new API key#
4. Start a new key and name it#
Click Create new secret key at the top right. In the Create New Subscription Key window, enter a Key Name. The name is optional, but a clear name, such as the integration that will use it, makes the key easier to manage later. The window also shows the rate limits and quotas that apply to your keys.5. Choose permissions#
Under Permissions, choose one of:All: Full read and write access to every API category. This is the default.
Read Only: Can only call GET endpoints across every category. No write access.
Restricted: Choose access per API category, such as Agents, Corpora, Projects, or Users. For each category, pick None (no access), Read (GET requests only), or Write (all requests, including GET, POST, PUT, and DELETE).
6. Create the key#
7. Copy your secret key#
Click the copy icon to copy the key, store it somewhere safe, and click Done.The secret key is shown only once. If you lose it, you'll need to create a new key.
8. Find your key in the list#
Your new key appears in the list with its permission and a Connected status.
Change a key's permissions#
9. Edit the permission scope#
Click the edit (pencil) icon next to the key. In Edit Subscription Key Permission, choose a different permission and click Save Changes. The key itself isn't rotated, so integrations using it keep working with the new permissions.
Revoke a key#
10. Revoke the key#
Click the delete (trash) icon next to the key you want to remove, then click Revoke. The key is disabled immediately and removed from the list. Any requests that still use it will be rejected, so update those systems first.
Test your key#
Every request needs your Server URL as the base URL, plus two headers:Ocp-Apim-Subscription-Key: {your-api-key}
Authorization: Bearer {your-access-token}
FAQs#
What happens if my integration goes over the rate limits?#
Requests are temporarily blocked until the time window resets. Click Rate Limits & Quotas on the API Keys page to see your limits.Do rate limits apply to each key separately?#
No. Rate limits and quotas depend on your role and apply to all your API keys together.How do I see which requests failed?#
Click Show Logs on the API Keys page. Audit Logs lists each request with its response code, error details, caller IP address, and URL. 