Create and manage API keys
A website script uses a public product ID (prd_8f3kq2m9x1). Authenticated APIs use secret, website-scoped API keys (jk_…). Keep those keys on your server.
Create a key
- Open Settings → Developer → API keys.
- Choose Create API key, name its purpose and select only the required scopes.
- Copy the full value when shown. Store it in your server's secret environment; it is shown once.
- Verify the intended operation with the Website API guide.
| Scope | Purpose |
|---|---|
analytics:read |
Read analytics reports and health. |
funnels:read |
Read funnel definitions. |
funnels:write |
Create, edit and delete funnels. |
payments:write |
Submit verified custom payments and refunds. |
crawlers:write |
Send server crawler observations and connection checks. |
Scroll horizontally to see more columns on smaller screens.
Do not put a key in website JavaScript, a distributed desktop app, an iframe embed or an AI-builder prompt. A prd_ product ID cannot replace it for authenticated endpoints.
Rotate or revoke
Create a replacement with the necessary scopes, update the server secret and verify it, then revoke the old key. Existing keys do not automatically acquire new scopes. Review integrations when a team member loses access: their issued keys can be revoked by the role change.
If a request is unauthorized, check the key's product, scope and revocation state before widening its permissions.
Delete a revoked key
In Settings → Developer → API keys, choose Delete next to a revoked key and confirm. The key is removed from the list and remains invalid. Active keys must be revoked before they can be deleted.
Connect an assistant
Use MCP for analytics and authorized product tools. An API key grants only that product's basic metadata, analytics and funnels. For selected products, OAuth sign-in avoids manual credential handling. Account tokens beginning with jt_ can additionally authorize product creation and scoped credential management; create them in Account settings → API / MCP.