Skip to main content
All v2 endpoints require your API key as a Bearer token:

Geocoding Key

Location-based endpoints (/v2/charts and /v2/charts/simple) additionally require a Google Geocoding API key:
This key is used to convert location strings (e.g., “Amsterdam, The Netherlands”) into geographic coordinates. You can get one from the Google Cloud Console.
The coordinates endpoint (/v2/charts/coordinates) does not need a geocoding key. If you already have latitude and longitude, use it to skip geocoding entirely.

Full Request Example

v1 Authentication (Legacy)

v1 uses a different header format. New integrations should use v2. See the migration guide.
v1 endpoints require two custom headers:
The same API key works for both v1 and v2 — only the header name changes.

Access Tiers

Your plan determines which endpoints you can access: Calling an endpoint above your tier returns 403 with error code ACCESS_DENIED.

API Key Security

Keep your API key secret. Never expose it in client-side code, public repositories, or browser requests.
  • Your API key is available in the dashboard
  • If your key is compromised, rotate it immediately from the dashboard. The old key is invalidated instantly
  • Each API call deducts one credit from your plan’s allocation

Authentication Errors