Skip to main content
Beta. AgentSource v2 is in beta. Details may still change before GA.

​
There is no hard cutover

v2 ships alongside v1. v1 keeps running in parallel and is wound down in stages, so you have a full migration window and can move at your own pace.

​
v1 deprecation timeline

Timing is indicative and subject to minor change. T0 is v2 GA.

​
Migration steps

1

Move to /v2 paths

Replace the /v1 prefix with /v2 on every endpoint. See the mapping below.
2

Collapse bulk calls into single endpoints

Drop the /bulk_enrich suffix. The single endpoint accepts one ID or a list of IDs, so a bulk call becomes the same endpoint with a list payload.
3

Pick sync or async

Use .../enrich for immediate results, or .../job for large runs. Async is capped at 10K input records and 24 hours per job.
4

Update renamed paths and fields

Rename contacts_information to contact_information, and update the corrected signal field names.
5

Handle removed response fields

Stop reading entity_id, display_name on business LinkedIn posts, and the address signals on company_ratings_by_employees.
6

Check changed fetch defaults

Remove the size pagination parameter, and set include_operating_locations explicitly if you relied on the old default.

​
Endpoint mapping

​
Breaking changes checklist

  • /v2 path prefix applied everywhere
  • /bulk_enrich calls collapsed into /enrich or /job
  • contacts_information renamed to contact_information
  • founding_stage → funding_stage, founding_date → funding_date
  • professions_email → professional_email
  • entity_id no longer read
  • display_name no longer read from business LinkedIn posts
  • Address signals no longer read from company_ratings_by_employees
  • size pagination parameter removed
  • include_operating_locations set explicitly
  • Async payloads within the 10K record limit
  • Autocomplete calls pointed at /v2/autocomplete

What's new

The full change list

Conventions

Rules that apply across every v2 endpoint