Skip to main content

​
API keys

Create a key from Dashboard → API Keys. Send it on authenticated data requests:
Use the API key header, rather than your dashboard session cookie or a query-string key. Dashboard login and public API authentication are separate flows.

​
Public and authenticated routes

GET /v1/me identifies your account and current key without consuming data quota. Successful data requests count against the account’s shared monthly allowance.

​
Keep keys on your server

Store keys in server environment variables or a secret manager. Do not include them in frontend JavaScript, public repositories, screenshots, or customer-facing HTML. Each key’s full secret is shown only when it is created. If a key is lost or exposed, revoke it in the dashboard and create a replacement. All keys share the same account-wide rate limit and monthly quota.

​
Authentication errors

A 401 means the key is missing, invalid, revoked, or attached to an inactive account. Verify the header and check key status in the dashboard before retrying. See errors and limits for 429 responses and production retry behavior.