​
Introduction

FullEnrich is designed to help you enrich your contacts at scale using data from more than 20 providers, with a strong focus on quality and coverage. The API is asynchronous by design: you send enrichment requests and receive results via webhooks as soon as they’re ready. This approach supports both real-time integrations and large-scale bulk jobs.

​
API Endpoint Reference

All technical details, request/response payloads, and code snippets are available in our For quick reference, here are the main endpoints you’ll use (insert Mintify cards/blocks here as per your doc style):

Start Bulk Enrichment

Get Enrichment Result

Credits Left

Always refer to the main documentation for up-to-date specs.

​
Asynchronous Model & Result Retrieval

All enrichment requests are asynchronous. You send the request, and results are available as soon as they’re ready. Most enrichments take between 30 and 90 seconds, depending on provider response time. 2 Ways to Get Your Results: Webhooks are notifications sent directly to your server when results are ready. Instead of you having to check for results, we push them to you immediately (fastest way to get enrichment results). FullEnrich is designed for asynchronous usage, and webhooks are the only recommended way to receive enrichment results. When your enrichment is done, we POST the result directly to the webhook URL you provide. This means you don’t have to keep a connection open or handle HTTP timeouts, retries, or connection errors. For most product teams, this is both simpler, faster, and much more reliable than managing long-running requests yourself. Webhooks are reliable by design. If, for any reason, we can’t deliver your result (for example, a network issue on your server), we’ll automatically retry delivery 5 times. For most use cases, you can treat webhooks as “guaranteed delivery.” If there’s ever a question about a specific result or missed event, our team can check our delivery logs on request. Easy webhook implementation: You can easily keep track of which enrichment belongs to which user or request by using the custom parameter when creating an enrichment. For example, you can include a User ID, Enrichment ID, or any other value that helps you match the result to your internal data. This value will be sent back to you exactly as provided, inside the custom object in the webhook payload. Example usage: 
"custom": {
    "user_id": "12584"
}
Polling means repeatedly checking an endpoint to see if the enrichment is finished. This method requires you to actively check for results at regular intervals. Polling is not encouraged because it will consume your rate limit quota without benefit. If you have to implement polling, we recommend not polling more than once every 5–10 minutes. Never poll every few seconds.
Key Considerations Retention: There is an unlimited retention period: once a contact is queued for enrichment, it will remain there until processed. There’s no automatic expiry or “timeout” for jobs in the queue.