Skip to main content
POST
Prospects Contact Information Job

Description

The Asynchronous Contact Information Enrichment retrieves verified emails, phone numbers, and mobile numbers for up to 10,000 prospects per job — and, unlike the synchronous endpoint, it supports waterfall enrichment: prospects that Explorium data cannot enrich are automatically retried against a verified external provider, increasing overall contact coverage. Key Benefits:
  • Asynchronous retrieval of enriched contact data for up to 10,000 prospects per job.
  • Higher coverage — the optional waterfall falls back to an external provider for prospects with no Explorium contact data.
  • Source transparency — every result is tagged with where its email and phone came from.
Asynchronous variant. This submits a job through the async job infrastructure — poll job status for progress and results. Input comes from an uploaded dataset (list_id); limits are 10,000 rows and a 24-hour run time.For the output signal reference shared with the sync endpoint, see Contact information.

Parameters

waterfall is only available on this asynchronous endpoint. Passing it to the synchronous /enrich endpoint returns a validation error.

How the waterfall works

With waterfall: "full", each job runs five steps:
1

Explorium enrichment

All prospects in the dataset are enriched with Explorium contact data. A prospect counts as enriched if at least one email or phone number is returned.
2

Identify gaps

Prospects with no email and no phone from Explorium are collected.
3

External fallback

The unenriched prospects are sent to the external provider, and its results are mapped onto the same contact schema (emails, phone_numbers, mobile_phone, professional_email_status).
4

Merge and return

One unified result set covers all prospects, with email_source and phone_source tagging where each value came from.
5

Credits charged by source

Explorium-sourced and externally-sourced results are charged at different rates — see Credit charging.

Example request

The list_id comes from the dataset upload endpoint — see the end-to-end guide for the full flow.

Response

Poll job status with the returned job_id. A finished waterfall job reports per-source totals under additional_data, alongside the usual credit usage:
Job status (completed)

Result fields

Results are downloaded as a CSV from results.download_url. The link is valid for about an hour (expires_at) — re-poll job status for a fresh one; the file itself is kept for 7 days (file_expires_at). Each row carries the contact data plus its source tags: Prospects that neither source could enrich are still returned, with the contact columns empty — and cost nothing.

Credit charging

Credits are charged per result, according to the source that produced it: For example, a prospect whose email came from Explorium and whose phone came from the external provider costs 2 + 24 = 26 credits. With waterfall: "explorium_only" (or the parameter omitted), behavior, response contract, and credit charging are identical to the endpoint as it works today — the waterfall adds cost only when the external provider actually returns data.

Best practices

  • Start with explorium_only to see your Explorium-native coverage, then rerun the gaps with full if you need more.
  • Use contact_types to control spend — externally-sourced phones cost significantly more than emails, so request only what you need.
  • Check additional_data on the job status to see how many results each source contributed before downloading.
  • Filter by email_source / phone_source downstream if you track data provenance per record.

Authorizations

api_key
string
header
required

Body

application/json
list_id
string
required

Entity ID list identifier returned by the upload endpoint

parameters
AsyncContactsEnrichmentParams · object

Response

Successful Response

job_id
string
required
status
string
required
status_url
string
required