SavvyIQ v3 API
Version 2026-08-05
The SavvyIQ API resolves business identity. Give it a name or a domain; get back a stable entity ID anchored to a government registration, plus the record we hold for that company.
Preview. The /v3 surface is in preview. Endpoints and fields may change before general
availability.
How the endpoints fit together
Two entry points resolve an identity; one endpoint returns the record.
| You have | Call | You get |
|---|---|---|
| A company name | GET /v3/entity-resolution/async, then GET /v3/jobs/{job_id} |
A siq_ entity ID |
| A domain | GET /v3/domain-intelligence |
A siq_ entity ID, plus what the domain is |
A siq_ entity ID |
GET /v3/entities/{id} |
The full record |
Resolve once, store the siq_ ID, and read the record from /v3/entities/{id} from then on.
IDs are stable.
One entity shape
Every endpoint serves the same identity core: legal_name and display_name, status,
description, website, headquarters, typed identifiers[], and primary_legal_entity,
the government registration that anchors the record.
The endpoints differ only in how much they add on top. Entity resolution adds facets
(ownership and legal form) and scheme-keyed industry codes under industry.schemes.
/v3/entities/{id} adds those plus the enrichment: firmographics, classification labels,
operational footprint, social profiles. /v3/domain-intelligence serves the identity core
alone, next to everything it knows about the domain itself.
Base URL
https://api.savvyiq.ai Endpoints
Entity Resolution
Entity Record
Domain Intelligence
Guides
- Quickstart Every request needs an apikey header.
- Concepts Entities and candidates An entity is a confirmed record, anchored to a government registration.
- Authentication Authenticate with an API key sent in the apikey header.
- Rate limits Limits are per minute, per key, and differ by endpoint.
- Codes & enums Closed vocabularies used across /v3 responses.