​
API key authentication

API keys authenticate all programmatic access to EESI — the REST API, WebSocket connections, the SDKs, and the MCP server. Pass your key as a Bearer token in the Authorization header:
The X-API-Key header is also accepted for backwards compatibility:
For WebSocket connections, pass the key as a query parameter instead: ?api_key=sk-eesi-.... API keys are scoped to an organization. All resources created or accessed using a key belong to that organization.

​
Key format

Keys are OpenAI-style tokens that start with sk-eesi-. The full key is shown only once at creation time; afterwards the dashboard displays only the key prefix and last four characters (for example sk-eesi-…abcd), so store the full key immediately in a secrets manager or environment variable.

​
Create an API key

Create keys in the dashboard on the API Keys page (/api-keys). Sign in to the dashboard first, then create a key there before making API calls.

​
Manage API keys

Archiving a key immediately revokes it. All subsequent requests using that key return 401.

​
Error responses