Data and account

Authentication

Create, use, rotate, and revoke your account API keys.

Create a key

Sign in and open API keys in your dashboard. Give each integration a named key so you can identify and revoke it independently.

The full key is shown only when it is created. Save it in a private environment variable or your client’s secret configuration.

Authenticate requests

Set the bearer authorization header in your MCP client’s private configuration.

Authorization header

Authorization: Bearer <your-account-api-key>

See MCP client setup for client-specific examples. The REST API uses the same bearer header and also accepts X-API-KEY.

Rotate and revoke

Create a replacement key, update your integration, and revoke the old key in the dashboard. Revocation blocks the next data request or MCP tool call, including calls from an existing connection.

A missing or invalid key returns 401. A suspended or closed account cannot access data. Temporary authorization service failures return 503.

Creating another key does not add another allowance. All of your keys share the same account usage.