Fill a campaign with prospects from the contact database
Queues a background job that searches Emailchaser's internal contact database with the targeting criteria of an Ideal Customer Profile, reveals matching people and adds them to the campaign as leads. The profile defaults to the workspace's primary ICP when icpId is omitted. Sourcing is asynchronous: poll GET /leads?campaignId= to watch the prospects arrive. Each stored prospect costs the reveal price in credits (1 at the time of writing), reported per request as creditsPerProspect with the batch ceiling as estimatedCredits; duplicates, blocklisted domains and contacts without an email address are filtered out before any credit is spent. Repeated calls for the same campaign and profile resume the same search at its provider cursor, so they page deeper into the audience instead of re-revealing (and re-paying for) the same people.
Request
- Base URL: https://api.emailchaser.com/r
- URL: https://api.emailchaser.com/r/prospects/source
- Auth: HTTP bearer
Request body
Example request
{
"campaignId": 123,
"count": 50,
"icpId": 7
}Response
Sourcing job queued
Example response
{
"campaignId": 123,
"creditsPerProspect": 1,
"estimatedCredits": 50,
"icpId": 7,
"prospectSearchId": 42,
"requested": 50,
"status": "queued"
}Changes
No recorded changes to this operation across all 1 revision of this API.