Skip to main content
These rules hold across the whole v2 surface, so they are not repeated on individual endpoint pages.

​
Path versioning

Every endpoint moves under the /v2 path, replacing its /v1 equivalent.

​
No more bulk endpoints

A single endpoint accepts either one ID (a string) or a list of IDs. The separate /bulk_enrich routes are removed.
IDs are the primary way to call a sync enrichment. As an alternative, every sync enrichment except Research also accepts up to 50 businesses_to_match or prospects_to_match (the same inputs as the match endpoints) and matches and enriches them in one call. Send either the IDs or the match inputs, never both. Each enrichment page shows an example.
Match inputs instead of IDs

​
Sync vs. async pairing

Each enrichment exposes two endpoints:
The “single ID or a list of IDs” rule above applies to sync endpoints. Async .../job endpoints take a list_id from the dataset upload endpoint and do not accept inline IDs — see the end-to-end guide.
Both are POST. The async variant is subject to the async job limits: max 10K input records and a 24-hour maximum run time.

Async jobs

How job submission, polling, and retrieval work

Migrating from v1

Apply these conventions to your existing calls