Documentation
Authentication
How keys are scoped, stored and validated on every request.
Bearer tokens
Pass the key in the Authorization header. There is no query-string alternative, which keeps secrets out of access logs and browser history.
Header
Authorization: Bearer data_live_xxxxxxxxxxxxxxxxKeys are scoped to one product
A data_live_ key authenticates the Global Data product and nothing else. Presenting it to the geolocation or currency APIs answers 403 with product_access_denied. Each product also carries its own subscription, quota and key allowance.
Live and test prefixes
- data_live_ for production traffic.
- data_test_ for staging and local development.
- Both consume the same plan quota, so treat test volume as real volume.
Storage and rotation
Only a prefix and a secure hash are stored, so the platform cannot show you a key again after creation. Rotating a key issues a new secret and invalidates the previous one immediately, with no overlap window.