GoddsAPIFree API key
GoddsAPI Docs

Quick start

  1. Create a free account and confirm your email.
  2. Create a key on Dashboard → API keys. It's shown once; we keep only a hash.
  3. Make a request:
curl -G "https://goddsapi.com/api/v1/search" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "q=coffee shop" \
  --data-urlencode "location=Chicago, Illinois, United States"

Authentication

Send your key in a header — Authorization: Bearer gdd_live_… — or, where you can't set headers, as ?api_key=. Keys never appear in our logs in full. Revoke a leaked key on the API keys page; it stops working immediately.

Response format (v1)

Every success has search_metadata (id, status, provider, time_taken_ms, cached, credits_charged), search_parameters (what we searched, after defaults), then the results. Arrays are always present, even if empty; fields are always present, null when unknown. New fields may be added to v1; nothing is renamed or removed without a new version.

Caching

Identical searches — compared after normalizing case and spacing — are answered from cache for your plan's cache window (1 hour by default) and cost nothing: search_metadata.cached is true and X-Cache: HIT. Your cache is private to your account. Add no_cache=true to force a fresh, charged search.

Quotas and billing dates

Your monthly quota resets on your billing date. Every response carries X-Quota-Remaining; /api/v1/account returns the full picture for free. When the quota runs out, Free plans get 402; paid plans keep working at the published overage price.

Where results come from

GoddsAPI doesn't scrape Google itself. Results come from established SERP data providers and are normalized into this schema. If a provider errors or times out we automatically try the next one; search_metadata.provider tells you which one answered.

Next

See each endpoint's parameters on the left, and errors, limits & headers.