API - getdomaindata.com

In one call

curl https://getdomaindata.com/api/v1/domain/allbirds.com \
  -H "Authorization: Bearer gdd_live_YOUR_KEY"

The answer is the profile we serve on the site: technologies, network, platform, identity fields, and the latest traffic and employee estimates where we hold them. Start with the quickstart or go straight to the endpoint reference.

The basics

Base URLhttps://getdomaindata.com/api/v1

AuthenticationOne header on every request: Authorization: Bearer …

ResponsesJSON. {"data": …} on success, {"error": "code"} on failure, standard status codes.

MeteringOne lookup is one domain queried. Counts and the catalog are free. Every response carries X-Quota headers.

Versioningv1 in the path. Changes are additive; the changelog records each one.

Endpoints

Reference

GET /domain/{domain}1 lookup POST /domains/batch1 lookup per domain, found or not POST /enrich1 lookup GET /traffic/{host}1 lookup GET /employees/{host}1 lookup GET /technology/{name}Free GET /meta/technologiesFree

Who can use it

API access comes with a paid plan. A free account has 0 lookups, so the first step is choosing a plan on the pricing page; keys are then created on your account page.

Not writing code? The Google Sheets and Excel page has a copy-and-paste recipe, and the Clay page sets up one column that fills a whole table. Building with an assistant? The whole documentation is one file at /docs/api.md and the spec is at /openapi.json.