# Business Intelligence API

Read the full record for a resolved entity by its siq_ ID. Firmographics, industry codes, operational presence, social profiles, identifiers. One GET, never blocks.

## What it is

`GET /v3/entities/{id}` returns everything we hold for an entity: the identity core shared with resolution, plus the enrichment. Resolve once (by [name](/docs/apis/entity-resolution) or [domain](/docs/apis/domain-intelligence)), store the `siq_` ID, and read the record from here from then on.

- **Input:** a `siq_` entity ID. `le_` and `op_` IDs are not lookup keys and return `400`.
- **Output:** one entity object with `attributes`, `classification`, `industry`, `operational_presence`, `social_profiles`, `identifiers` and `facets`.
- **Never blocks.** The endpoint serves what exists now and reports the build state in `enrichment.status`.

> **New to entity IDs?** [Identifiers](/docs/concepts/identifiers) explains the three ID levels. [Entities and candidates](/docs/concepts/entities-and-candidates) explains why a candidate has no ID.

## Enrichment lifecycle

`enrichment.status` on every response:

- `pending` or `building`: the first read of a never-enriched record starts the build in the background. Poll until `complete`; every 10 seconds is plenty.
- `refreshing`: current data is served while a background refresh runs.
- `complete`: data is ready and current.
- `failed`: the build could not complete.

Registry data updates on each registrar's cadence; web-sourced enrichment refreshes periodically.

## Merged records

`siq_` IDs are stable. If two records were consolidated, the response returns `status: "merged"` with `merged_into` set, and serves the canonical record. Store the new ID.

## Request

```bash
curl 'https://api.savvyiq.ai/v3/entities/siq_33d67jj0wJESjEdFHMhuQ' \
  -H 'apikey: YOUR_API_KEY'
```

## Example response

Datadog, verbatim from the reference capture, with `description` shortened.

```json
{
  "status": "matched",
  "merged_into": null,
  "entity": {
    "id": "siq_33d67jj0wJESjEdFHMhuQ",
    "display_name": "Datadog",
    "legal_name": "DATADOG, INC.",
    "status": "active",
    "type": "business",
    "subtype": "incorporated_entity",
    "description": "Datadog is a leading cloud monitoring and security platform ...",
    "website": "https://www.datadoghq.com/",
    "headquarters": {
      "address": {
        "street_address": "620 8th Ave, 45th Floor",
        "city": "New York",
        "state": "New York",
        "state_code": "NY",
        "postal_code": "10018",
        "country": "United States",
        "country_code": "US",
        "formatted_address": "620 8th Ave, 45th Floor, New York, New York 10018, United States"
      }
    },
    "primary_legal_entity": {
      "id": "le_2Zp3Yy6S7O6Btccq56WOH",
      "jurisdiction": "US-DE",
      "state_code": "DE",
      "country_code": "US",
      "registration_authority": {
        "id": 1024,
        "code": "RA000602",
        "name": "Division of Corporations, Department of State",
        "jurisdiction": "Delaware",
        "country_code": "US",
        "website": "https://corp.delaware.gov/"
      }
    },
    "identifiers": [
      { "type": "registration_id", "value": "4832851", "jurisdiction": "US-DE" },
      { "type": "cik", "value": "0001561550", "jurisdiction": null },
      { "type": "lei", "value": "549300F6JNO0KRPO1K63", "jurisdiction": null }
    ],
    "attributes": {
      "domain": "datadoghq.com",
      "employee_count": 3001,
      "employee_range": "1K-5K",
      "revenue": 3672030976,
      "revenue_range": "$1B-$10B",
      "founding_date": "2010-01-01",
      "stock_ticker": "DDOG",
      "exchange": "NASDAQ",
      "is_public": true,
      "market_cap": 91027922944,
      "funding_total_usd": null,
      "funding_rounds_count": 10
    },
    "classification": {
      "sector": "Technology",
      "industry": "Computer Software",
      "sub_industry": "Cloud Software",
      "business_tags": [ "Cloud Monitoring", "Observability", "SaaS", "AIOps", "Application Performance Monitoring", "Cloud Security", "IT Infrastructure Monitoring", "DevOps Tools" ],
      "market_segments": [ "b2b" ],
      "revenue_models": [ "subscription" ],
      "products_services": [ "Infrastructure Monitoring", "Application Performance Monitoring (APM)", "Log Management", "Cloud Security", "Digital Experience Monitoring", "Network Performance Monitoring" ]
    },
    "operational_presence": [
      { "id": "op_33ZbC5x7TWMqjRnGBE88L", "country_code": "US", "country": "United States of America", "count": 4, "is_home_jurisdiction": true }
    ],
    "social_profiles": {
      "crunchbase": { "handle": "datadog" },
      "linkedin": { "handle": "company/datadog" },
      "facebook": { "handle": "datadoghq" }
    },
    "facets": { "sector": "public", "legal_form": "corporation" },
    "industry": {
      "schemes": {
        "naics_2022": [
          { "code": "513210", "label": "Software Publishers", "is_primary": true, "confidence": 95 },
          { "code": "541511", "label": "Custom Computer Programming Services", "is_primary": false, "confidence": 80 },
          { "code": "51", "label": "Information", "is_primary": false, "confidence": 90 }
        ],
        "sic": [ { "code": "7372", "label": "Prepackaged Software", "is_primary": true, "confidence": 95 } ]
      }
    }
  },
  "request_id": "req_344u0qy2y3M8aaO9EGfL4",
  "enrichment": { "status": "complete", "updated_at": "2026-07-31T19:22:05.042Z" }
}
```

## What you get

- **Industry:** `industry.schemes` keyed by scheme (`naics_2022`, `sic`), primary code first, each with a per-code `confidence`. A scheme that was not classified is absent.
- **Classification:** sector and industry labels, `business_tags`, `products_services`, and the business-model axes `market_segments` and `revenue_models`, ordered most-material-first.
- **Firmographics:** `attributes` with employee and revenue ranges, founding date, listing details where public. `null` means unknown, never zero.
- **Operational presence:** the countries the entity operates in, with the count of registrations we hold and which is home.
- **Identity:** `legal_name`, `display_name`, `primary_legal_entity`, typed `identifiers[]`, `facets`.

Ownership is a separate research surface: [Entity Hierarchy](/docs/apis/entity-hierarchy) takes the same `siq_` ID.

## Reference

- [`GET /v3/entities/{id}`](/docs/reference/entity-record/get-v3-entities-id/)
- [Codes & enums](/docs/guides/codes-enums) for every enum on this record

The v1 endpoint (`/v1/entities/{entity_id}`) keeps working; its reference is the [2026-07-30 edition](/docs/reference/2026-07-30/).