Skip to main content
Create Analytics API tokens from your Embedder account. The token must include the analytics:read scope.
Analytics is available to enabled organizations. If the scope or Analytics pages are unavailable, contact your Embedder representative.

Create the token

1

Open your account

Sign in to app.embedder.com, open Account, and select the Tokens tab.
2

Start a new token

Select Create token. Give the token a name that identifies the integration or job that will use it, such as analytics-dashboard-prod.
3

Choose an expiration

Select 30 days, 60 days, 90 days, one year, or no expiration. Prefer the shortest lifetime your integration can rotate reliably.
4

Grant analytics access

Under Scopes, enable analytics:read. A token without this scope cannot read organization Analytics API data.
5

Generate and copy

Select Generate, then copy the token immediately. The complete value is shown only once.
Store the value in a secret manager or protected environment variable:
Do not commit the token, put it in a URL, or paste it into logs or shared configuration. Revoke it immediately if it is exposed.

Find your organization ID

Open Organizations in the web app and select the organization whose usage you want to read. Its URL has this form:
Copy the final path segment:
The token owner’s organization membership and role determine which data is available. A scoped token does not grant access to an organization the account cannot already access.

Test the token

Request an Analytics overview with an explicit ISO 8601 date range:
A successful request returns JSON containing totals, previous, and days. See the Analytics API reference for user, team, and session endpoints. If the request fails:
  • 401: check that the token was copied completely and has not expired or been revoked.
  • 403: confirm that analytics:read was selected, the organization ID belongs to the account, and Analytics is enabled for the organization.
  • 429: wait for the duration in the Retry-After response header before retrying.

Rotate or revoke a token

Create a separate replacement token before removing a token that is in use:
  1. In AccountTokens, create a new token with analytics:read.
  2. Put the new value in the integration’s secret store.
  3. Make a test request with the replacement.
  4. Update or restart every process that used the old value.
  5. Return to Tokens and delete the old token.
Use Regenerate token only when you can replace the current value immediately. The regenerated secret is also shown once.
Last modified on August 24, 2026