Get Enrichments
Enrichment
Get Enrichments
Discover available Enrichments and inspect a contract by slug.
GET
Get Enrichments
CLI:
Overview
Returns the catalog of Enrichments the workspace can run. Each Enrichment is a typed contract — slug, subject (person or company), input schema, output schema, and cost model.
Pass id (the Enrichment slug) as a query parameter to fetch one contract instead of the whole catalog. Hidden and internal Enrichments are excluded from normal discovery.
Use this endpoint before calling Enrich leads so an agent knows which enrichmentId values exist and what inputs each requires.
See also: Enrich leads · Enrichment status.
AI agent notes
The enrichment-discovery journey:
GET /api/enrichments— see which Enrichments exist (work_email,website_overview,hiring_status, …).GET /api/enrichments?id={slug}— inspect input schema, output schema, andcostModelfor the one you want.POST /api/enrichment— dispatch withenrichmentId: {slug}and a Lead scope.
subjecttells you whether the Enrichment expects person or company Leads. Passing the wrong subject in a Run returns aSUBJECT_MISMATCHplanner error.costModel.creditAction(when present) determines what credits will be charged. A missingcreditActionmeans the Enrichment is internal or free and is not credit-gated.- The Enrichment object shape varies by slug; treat it as
Record<string, unknown>and readslug,subject,inputSchema,outputSchema, andcostModeldefensively.
404: only fires when id is supplied and no matching visible Enrichment exists.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Response
List of Enrichments (omit id) or one Enrichment contract (with id).
- Option 1
- Option 2