Prospecting API
Prospecting is programmatically available under /v1/prospecting. A restricted
API key uses prospecting_read for reads and prospecting_write for mutations;
most automations need both. The key owner must have the Prospecting module and
the same organization access as in the app.
Search lifecycle
Run searches through the same review-before-spend lifecycle as the product:
POST /v1/prospecting/searchescreates a draft from structured criteria.POST /v1/prospecting/searches/:publicId/samplereturns a non-billable preview.POST /v1/prospecting/searches/:publicId/estimatestores the reviewed cap and enrichment choices.POST /v1/prospecting/searches/:publicId/approvestarts the billable run. It has no request body and cannot exceed the stored estimate.GET /v1/prospecting/searches/:publicId/resultspolls materialized results.
Use GET /v1/prospecting/searches to list searches and
GET /v1/prospecting/searches/:publicId to inspect status. Draft and previewed
searches can be refined with PATCH /v1/prospecting/searches/:publicId.
The exact criteria and response schemas are published in the full API reference. Once results exist, use campaign contact import to create or reuse Contacts and add them to an Outreach campaign in one atomic call.
For asynchronous candidate, application, LinkedIn, and message events, see outbound webhooks.