Academy
My Profile

API Keys: generate and revoke

API keys allow secure communication between external systems and Dattos — they are what authenticate the Dattos CLI, AI assistants via MCP, and API integrations. The key is personal: all actions performed with it are recorded as yours, and only your permissions on the platform apply — nothing more.

To access them, click your avatar (top right corner) and choose API Keys — or open the tab of the same name in My Profile.

Availability: API key generation may not be available on all plans or environments. If the option does not appear for you, contact the platform administrator.

Generate a key

  1. Click New API key.

  2. Fill in the Description (required, up to 100 characters) — identify the use, for example "financial pipeline CLI" or "Claude Assistant".

  3. If you want, set an Expiration Date (optional) — without a date, the key does not expire.

  4. Click Save. The key is shown on the next screen, with a copy button.

Attention — the key is shown only once. After you close the window, it cannot be viewed again. Copy it and store it in a safe place (a password vault) before closing; if you lose it, revoke it and generate a new one.

Track your keys

The tab list shows, for each key: the Description, the creation date, the Expiration Date (or "Never") and the Last access (or "Never", if it has not been used yet) — useful for identifying forgotten or unused keys.

Where the key is used

  • Dattos CLI: dattos config set api-key "<sua chave>" — see "Dattos CLI: installation and first steps".

  • AI assistants (MCP): the key authenticates the MCP server — see "Connect AI assistants via MCP".

  • API calls: the key goes in the authorization header (Authorization: Bearer <sua chave>).

Revoke a key

In the key actions menu (three dots), choose Revoke and confirm. As the dialog itself warns: after revocation, any system using this key will lose access to Dattos — the operation cannot be undone. If the system is still needed, generate a new key and update its configuration.

Best practices

  • One key per system — this way, you can revoke one access without affecting the others, and the "Last access" remains trackable.

  • Do not share your keys — treat them like passwords; each user generates their own.

  • Use the expiration date for temporary access (a project, a test).

  • Review the list periodically and revoke anything that is no longer in use.

  • My Profile: data, language, and notifications

  • Dattos CLI: installation and first steps

  • Connect AI assistants via MCP

  • Introduction to integrations

Was this helpful?
Was this helpful?