Docs

Authentication

Every request to the GeoQ API is authenticated with an API key, sent as a Bearer token in the Authorization header.

API keys

• Keys look like geoq_live_xxxxxxxxxxxxxxxx.
• Create and revoke keys in your dashboard. Growth and Scale plans support multiple keys.
• Treat keys as secrets — never commit them or expose them in client-side code.

Sending the key

$ curl "https://api.geoq.io/v1/check?ip=8.8.8.8" \
    -H "Authorization: Bearer geoq_live_xxxxxxxxxxxx"

Where to call from

Call GeoQ from your server, not the browser, so your key stays private. The interactive widgets on this site call an unauthenticated public demo path with strict rate limits — that is not how you should integrate in production.

Rotating keys

Create a new key, deploy it, then revoke the old one. Both work during the overlap so you can rotate with zero downtime.

# 12-factor style: keep the key in the environment
export GEOQ_API_KEY="geoq_live_xxxxxxxxxxxx"

Unauthenticated requests

A request with no key, or an invalid/revoked key, returns 401 Unauthorized. See errors.