# Domain Intelligence API

Identify the legal entity that operates a domain, website URL, or email address, and what the domain itself is for. One GET; answers in seconds for a domain we hold.

## What it is

`GET /v3/domain-intelligence?domain=…` answers two questions at once: **which legal entity operates this domain**, and **what is this domain for**. The entity half is the same identity core as resolution (a `siq_` ID anchored to a registration, or a `candidate`); the domain half is everything we know about the domain itself.

- **Input:** a bare domain, a full URL, or an email address. All normalize to the root domain.
- **Output:** `data.entity` (or `data.candidate`) plus `data.domain_intelligence`.
- **Timing:** a domain we already hold answers in seconds. A new one returns `status: "building"` and completes in a few minutes; poll, or pass `webhook_url` and get the result delivered.

The company name on a website is not the legal entity that operates it. `office.com` is Microsoft Corporation. The entity half is what makes that determination.

## Status lifecycle

Top-level `status`:

- `building`: analysis and entity resolution in progress; `data` is `null`
- `complete`: both halves are ready
- `refreshing`: current data served while a background refresh runs
- `failed`: analysis could not complete

## Request

```bash
curl 'https://api.savvyiq.ai/v3/domain-intelligence?domain=datadoghq.com' \
  -H 'apikey: YOUR_API_KEY'
```

Also accepts `POST` with a JSON body: `{"domain": "datadoghq.com"}`.

Optional: `webhook_url` and `custom_id`, the same per-call delivery as resolution. See [Webhooks](/docs/guides/webhooks).

## Example response

Datadog, verbatim from the reference capture, with the two descriptions shortened.

```json
{
  "domain": "datadoghq.com",
  "status": "complete",
  "data": {
    "status": "matched",
    "confidence": 98,
    "type": "business",
    "subtype": "incorporated_entity",
    "entity": {
      "id": "siq_33GtdRpeJrG8n7orm8iI2",
      "display_name": "Datadog",
      "legal_name": "DATADOG, INC.",
      "status": "active",
      "description": "Datadog is a technology company specializing in monitoring and analytics for cloud applications ...",
      "website": "https://www.datadoghq.com/",
      "headquarters": {
        "address": { "street_address": "620 8th Ave 45th Floor", "city": "New York", "state_code": "NY", "postal_code": "10018", "country_code": "US" }
      },
      "primary_legal_entity": { "id": "le_33GtddNjSzLpgddO2Yy6y", "jurisdiction": "US-DE", "state_code": "DE", "country_code": "US" },
      "identifiers": [ { "type": "sec_cik", "value": "1561550" } ],
      "matching_branch": null
    },
    "candidate": null,
    "factors": [
      { "code": "website_official_status", "type": "strength", "impact": "Confirms this is the entity's official website.", "description": "The domain 'datadoghq.com' clearly functions as the official website for Datadog." },
      { "code": "legal_entity_confirmed_on_website", "type": "strength", "impact": "Confirms the legal entity operating this domain.", "description": "The legal entity 'DATADOG, INC.' is identified and confirmed within the domain's legal information." },
      { "code": "domain_content_matches_entity", "type": "strength", "impact": "Confirms this is the entity's official domain.", "description": "Domain content, branding, and services on 'datadoghq.com' strongly align with Datadog's operations." },
      { "code": "consistent_entity_references", "type": "strength", "impact": "Eliminates ambiguity about domain ownership.", "description": "Multiple pages across 'datadoghq.com' consistently reference Datadog and its corporate identity." }
    ],
    "actions": [],
    "domain_intelligence": {
      "domain": "datadoghq.com",
      "url": "https://www.datadoghq.com/",
      "domain_aliases": [],
      "description": "Datadog, Inc. is an American technology company that provides a cloud monitoring and analytics platform ...",
      "tranco_rank": 739,
      "website_status": {
        "status": 200,
        "is_resolvable": true,
        "is_webserver_responsive": true,
        "has_content": true,
        "failure_reason": null,
        "last_checked": "2026-06-28T23:17:06.745Z"
      },
      "social_profiles": {
        "linkedin": { "handle": null },
        "facebook": { "handle": null },
        "crunchbase": { "handle": null },
        "twitter": { "handle": null }
      },
      "classification": {
        "sector": "Technology",
        "industry": "Software",
        "sub_industry": "Enterprise Software",
        "market_segments": [ "b2b" ],
        "revenue_models": [ "subscription" ],
        "products_services": [ "Infrastructure Monitoring", "Application Performance Monitoring (APM)", "Log Management", "Security Monitoring", "Digital Experience Monitoring (DEM)", "Cloud Cost Management", "AI-powered insights" ],
        "business_tags": [ "Cloud Monitoring", "Observability Platform", "DevOps Tools", "IT Operations Management", "SaaS", "Data Analytics", "Cybersecurity", "Performance Management", "Cloud Computing", "Software Development" ]
      },
      "domain_context": {
        "domain_type": "corporate_website",
        "domain_relationship": "direct_owner",
        "domain_purpose": "The primary online presence for Datadog, Inc., used for marketing products, providing customer support, and hosting company information.",
        "business_relevance": "datadoghq.com is the official corporate website and a critical channel for Datadog to engage with customers, showcase its platform, and conduct its core business operations as a software provider."
      },
      "is_disposable_email_provider": false,
      "industry": {
        "schemes": {
          "naics_2022": [
            { "code": "513210", "label": "Software Publishers", "is_primary": true, "confidence": 95 },
            { "code": "51", "label": "Information", "is_primary": false, "confidence": 90 },
            { "code": "541511", "label": "Custom Computer Programming Services", "is_primary": false, "confidence": 80 }
          ]
        }
      }
    }
  },
  "message": null,
  "metadata": { "last_updated": "2026-08-10T01:49:37.992Z", "processing_started_at": null, "estimated_completion": null },
  "request_id": "req_344trDC0nwk1zbUrYegyQ"
}
```

## Reading the result

- **`data.entity`** is the identity core only: name, status, headquarters, `primary_legal_entity`, `identifiers`. For firmographics and the full industry set, read [`/v3/entities/{id}`](/docs/apis/business-intelligence) with `data.entity.id`.
- **`data.candidate`** is populated instead when we could not commit to a registration: a parked domain, a sole trader, a type we do not record yet. It has no ID. See [Entities and candidates](/docs/concepts/entities-and-candidates).
- **`data.confidence`** and **`data.factors`** explain the entity match. Note the score is named `confidence` on this surface and `match_confidence` on resolution.
- **`data.domain_intelligence`** describes the domain, not the company: `domain_context.domain_type` says what kind of site it is (`corporate_website`, `parked_domain`, `email_domain`, ...) and `domain_relationship` how the entity relates to it (`direct_owner`, `parent_company`, `service_provider`, ...). `classification` and `industry` here are domain-scoped: a product site classifies as the product, not the whole company.
- **`identifiers[]`** on this surface is served as stored (`sec_cik`, unpadded, no `jurisdiction`); the resolution and record surfaces canonicalize (`cik`, zero-padded). Treat the two as the per-surface difference they currently are.

Every enum is listed in [Codes & enums](/docs/guides/codes-enums).

## Common integration

1. Submit the domain, URL or email.
2. If `status` is `building`, poll or wait for the webhook.
3. If `data.entity` is present, store `data.entity.id`.
4. Read the full record from `/v3/entities/{id}` when you need more than identity.

## Reference

- [`GET /v3/domain-intelligence`](/docs/reference/domain-intelligence/get-v3-domain-intelligence/)

The v1 endpoint (`/v1/domain-intelligence`) keeps working; its reference is the [2026-07-30 edition](/docs/reference/2026-07-30/).
