API access

Authenticate with a Dante API key and call the Dante API directly from your own code.

What the API is for

The Dante API lets your own scripts, dashboards, and back-end services talk to your workspace agents over HTTPS, without going through Zapier. You authenticate each request with a Dante API key that starts with dnt_. If you only need to wire your agent into another app, the Integrations page covers the no-code Zapier path instead.

Plan availability

The Dante API is available on Pro only. Every request is re-checked against your plan, so a workspace that leaves Pro loses API access even if a key was minted while it was still on Pro.

On Free, Starter, or Advanced? You can browse the Integrations tab, but generating a Dante API key is locked. Upgrade to Pro to use the API.

Generate a key

Integrations → Generate Dante API key. Give the key a name, then copy it. The full key is shown only once, so store it somewhere safe before you close the dialog. We keep only a hashed copy and cannot show it to you again.

Keys never expire. They keep working until you revoke them.

Authenticate your requests

Send the key in the Authorization header on every request, as a bearer token:

Authorization: Bearer dnt_your_key_here

A few rules to keep in mind:

The header is the only accepted place for the key. Passing it in the query string (for example ?api_key=) is not supported, so it cannot leak into proxy logs.
The base URL is https://agents.dante-ai.com/data-api/v1.
Each key belongs to one workspace, so requests act on that workspace automatically. You do not send a separate workspace header.

For example, to list your agents:

curl https://agents.dante-ai.com/data-api/v1/agents \
  -H "Authorization: Bearer dnt_your_key_here"

Scopes

A key's scope decides what it is allowed to do. You choose the scope when you create the key.

Scope	What it allows	How to get it
Read-only	Read data from your workspace agents, for example listing your agents and reading an agent's configuration.	Generate a key and leave the checkbox unticked. This is the default.
`write_customization`	Update an agent's prompt and welcome message.	Tick Allow editing agent prompt and welcome message when you generate the key.

A key has one scope, not both. A read-only key cannot make changes, and an editing key is scoped to updating the prompt and welcome message. If you need both, generate two keys.

What a key cannot do

Some actions always require signing in to the dashboard and are never available to an API key, whatever its scope:

Billing and subscription changes
Inviting, removing, or changing the role of teammates
Workspace settings and account deletion
Deleting an agent
Security settings, such as resetting the rate limit or credit cap
Rotating an agent's widget key

Calling one of these with a key returns 403.

Rate limits

Requests are rate-limited on two sliding one-minute windows:

Limit	Requests per minute
Per key	60
Per workspace (all keys combined)	600

Crossing either limit returns 429. Wait a minute and retry.

Error responses

Status	Meaning
`401`	The key is missing, malformed, or not valid. A revoked key also returns 401.
`402`	The workspace is not on the Pro plan. Upgrade to restore API access.
`403`	The key is valid, but its scope does not allow this action, or the endpoint is only available when signed in.
`429`	A rate limit was hit. Retry after about a minute.

Revoke a key

Integrations → the trash icon next to the key. Revoking takes effect immediately, anything using that key stops working at once, and the change cannot be undone. If your workspace leaves Pro, existing keys stop authenticating but stay listed so you can clean them up.

Still stuck? We'll help.

Every plan, including Free, comes with human support. If something isn't behaving the way you expect after following the steps above, send us a note and we'll get back to you within one business day.

Contact our team →