Enrichment is when you refresh existing records so your prospecting data is up-to-date.

Use the bulk people enrichment endpoint to enrich data for up to ten people with a single API call. To enrich data for a single person, use the people enrichment endpoint instead.

Apollo relies on the information you pass via the endpoint's parameters to identify the correct people to enrich. The details for each person should be passed as an object in the details[] array. When you provide more information, Apollo is more likely to find matches within its database. If you only provide general information, such as a name without a domain or email address, you may receive a 200 response, but the response indicates that no records have been enriched. Check match_confidence in the response to understand how confidently Apollo matched the submitted information:

• high: Apollo found a high-confidence match for the submitted person information.
• medium: Apollo identified a likely match with medium confidence.
• low: Apollo identified a possible match with low confidence.
• none: Apollo couldn't find a match for the submitted person information.

For standard requests, unmatched entries are returned as null. When you use waterfall enrichment, an unmatched result can return match_confidence: none.

By default, this endpoint doesn't return personal emails or phone numbers. Use the reveal_personal_emails and reveal_phone_number parameters to retrieve emails and phone numbers. If you set either of these parameters to true, Apollo attempts to provide emails or phone numbers for all matches. When you use reveal_phone_number, provide a valid webhook_url so Apollo can deliver completed phone enrichment results. Alternatively, set poll_only=true and poll webhook results with the top-level request_id_str. Poll only when phone_enrichment.status is pending. Do not use phone_enrichment.request_id. If the status is skipped or not_attempted, Apollo did not create a phone enrichment job and polling returns 404 request_id_unknown.

Webhook requirements:

• HTTPS Required: Your endpoint must be publicly accessible over HTTPS.

• Rate Limiting: Ensure your webhook endpoint can handle the volume of webhook traffic sent by Apollo.

• Idempotency: Apollo may retry webhook calls; your endpoint should be idempotent to handle duplicate payloads safely.

You can also use the run_waterfall_email and run_waterfall_phone parameters to run waterfall enrichment. Waterfall enrichment gives you broader data coverage by checking connected third-party data sources for contact emails and phone numbers. When your request includes a waterfall parameter, provide a valid webhook_url. Alternatively, set poll_only=true and poll webhook result with the top-level request_id_str returned by the response. Passing poll_only=true together with webhook_url returns a 400 error (WEBHOOK_URL_WITH_POLL_ONLY). Apollo returns an immediate synchronous response with demographic and firmographic data, along with a waterfall enrichment request status. Completed emails or phone numbers are delivered asynchronously to your configured webhook or made available to poll, depending on your request.