Enrichment
Query Batch Enrichment Status
Query the status of multiple enrichment tasks in a single batch request
POST
This endpoint allows you to efficiently check the status of multiple enrichment operations at once. Instead of making individual requests for each entity, you can query up to 200 enrichment tasks in a single batch request. This is particularly useful when polling for enrichment completion across multiple leads.
Authentication
This endpoint requires authentication with a valid organization context.Requests without a valid organization ID will receive a
400 Bad Request
response with the message “Organization ID is missing”.Request
An array of enrichment task queries. Each task specifies an entity and the
enrichment field to check. Constraints: - Minimum: 1 task - Maximum: 200
tasks per batch
Response
The response is an array of enrichment objects for tasks that have enrichment records. Tasks without existing enrichment records are omitted from the response.Array of enrichment status objects. May be shorter than the input if some
entities don’t have enrichment records.
Use Cases
Polling for Enrichment Completion
When you trigger batch enrichment for multiple leads, use this endpoint to poll for completion status:- Trigger batch enrichment via the enrichment trigger endpoint
- Store the entity IDs and fields being enriched
- Periodically call this endpoint to check status
- Process leads as their enrichments complete
Checking Pre-existing Enrichments
Before triggering new enrichments, use this endpoint to check which entities already have enrichment data, avoiding duplicate processing and unnecessary credit consumption.Error Codes
| Status Code | Error Code | Description |
|---|---|---|
400 | VALIDATION_ERROR | Invalid request body, empty tasks array, or exceeds 200 task limit |
401 | UNAUTHORIZED | Missing or invalid authentication |
500 | INTERNAL_ERROR | Server error during enrichment query |
Notes
- The response array may be shorter than the input tasks array if some entities don’t have enrichment records
- Enrichments that exceed the maximum processing time are automatically marked as
timeoutstatus - The
dataFoundfield isnullwhile enrichment is pending and becomestrueorfalseupon completion - This endpoint is read-only and does not trigger new enrichments or consume credits
- For efficient polling, consider implementing exponential backoff when checking for pending enrichments