Enrich contact and company data from LinkedIn, Hunter, Perplexity, and Tavily. Enrichments are asynchronous — create a request and poll or stream for results.
Standing config — set once, applies to every enrichment: AI prompts, ICP, scoring anchors, and source/threshold toggles live on the Enrichment Config endpoints (PATCH /v2/config).
Per-request override — for one job: pass options.instructions (free-text brief that supersedes the standing config in every dimension) or options.goal_override (legacy alias — prefer instructions; narrow: re-anchors priority_score only) on the POST /v2/enrichments body.
How enrichment works
GET /v2/enrichments/{id} or, for queued batches, stream via GET /v2/jobs/{id}/stream (SSE).Create, monitor, and approve single enrichments
Drill into sources, fields, and CRM impact
Enrich contacts in bulk from a HubSpot list
Batches use a preview → confirm flow. Preview shows you who will be enriched and the credit cost. Confirm queues the actual enrichments.
Errors follow RFC 9457 problem+json, returning a body with type, title, status, detail, and a machine-readable code.
| Code | Description |
|---|---|
400 | Invalid request body or missing required fields |
401 | Invalid or missing credentials (Bearer JWT or x-api-key) |
404 | Enrichment or batch not found |
429 | Rate limit exceeded |