Skip to main content
Keys are managed in the Chattler app, on the agent’s Integrations page, in the API access card (“Доступ по API”). No API call creates a key.

​
Create a key

1

Open the agent

In the app, open the agent you want to expose and go to its Integrations page.
2

Add a key in the API access card

Give the key a name and choose its permission:
  • read-only: list conversations and read messages.
  • full: everything above, plus the chat endpoints.
3

Copy the key now

The raw key is shown once, right after creation. It looks like this:
Only the secret part authenticates. The key_id part is public and is the key’s id everywhere in the dashboard. If you lose the secret, rotate the key.

​
Rotate a key

Rotation issues a new secret and invalidates the old one immediately. The key id, its conversations and its statistics stay attached to the same key, so rotation is the right answer to a suspected leak: nothing else changes.

​
Delete a key

Deleting a key removes it. From that moment every request with it fails with 401 invalid_api_key, indistinguishable from a key that never existed. Its conversations and request history stay readable in the dashboard. Deletion cannot be undone; create a new key instead.
Never ship a key in a browser bundle, a mobile app or any client you do not control. A key is a long-lived owner credential that spends the owner’s balance. Call the API from your own backend and rotate the key the moment you suspect it leaked.

​
Authenticate with the key

Only the Authorization header with the Bearer scheme is accepted. Query-string credentials are ignored, and no dashboard token or Browser-ID header is involved.
A key is bound to one agent. Using it against a different {agent_id} returns 403 agent_mismatch.

​
Statistics

The owner sees requests, failures, latency, tokens and the amount charged per key and per UTC day in the same API access card. Provider cost is never exposed; the amount shown is what was charged to the balance.