Skip to main content
GET
List the people found at a prospect's site
Getting someone to write to is deliberately two steps: first find out who works at a site, then buy an address only for the people you actually want. That split is what stops you paying for forty addresses when one person was the right one.
Requests are scoped to the brand your API key belongs to; an organization key passes the brand’s teamId. See Authentication.

Find people

Looks up the people worth pitching at one site or a batch of them - editors, writers, whoever can actually add the link. Nothing is bought here: you get names, job titles and seniority so you can decide. Body: prospectIds, or selection to pick prospects by filter instead. Optionally pass terms, 3-25 distinct job titles to match; omit it for the default editorial, SEO, marketing, and owner roles. A 400 is returned when one term contains another (for example founder and founders), since the longer one can never find anyone the shorter does not. Runs in the background and replies 202. The response has enqueuedCount, enqueuedProspectIds, skipped, and creditsCharged. Poll Outreach Prospects while each enqueued site’s status is finding_people, then read the result with List a prospect’s people. Costs 5 AI credits per site. A 402 means not enough credits. These sites are skipped, counted in skipped, and cost nothing, so a retry is safe:
  • sites whose search is already running
  • creator platforms, where the searchable domain belongs to the platform rather than the person
  • sites whose linkPlay is not outreach, because the link is not earned by writing to someone
  • prospects that already link to you (already-linked)
Re-running it on a site returns the next people, never ones the prospect already has; a site that yields nobody new is refunded. See Bulk prospect actions for the request reference and Get people search terms for suggested title groups.

List a prospect’s people

GET /v3/outreach/prospects/{id}/people Everyone found at one site, newest activity first (lastActivityAt).
For a link on a blog post, a content editor or head of content answers far more reliably than a founder. Read title, not seniority.
Related endpoints: Get one person, Remove a person, List every person, Choose who to write to.

Resolve email addresses

Use Bulk people actions with a selection of person ids. The page renders the request and response schemas from OpenAPI. Costs 10 AI credits per person actually looked up. Anyone who already has an address, is already enriched, is mid-lookup or is marked no_email is skipped and costs nothing, so a retry is safe. Each call returns eligibility and one result per person; when nobody is eligible nothing is charged. A 402 means not enough credits. Anyone with no findable address is refunded automatically.
There is no product cap on how many people you enrich at once, only a request-size bound well above any real contact list. The cost is per person, so check the count before you send it.

Addresses

Authorizations

Authorization
string
header
required

Your SnowSEO API key (sk_...).

Path Parameters

id
string
required

Prospect ID.

Response

200 - application/json

Default Response

people
object[]