LeadOcean + your sender: search, enrich and send emails automatically

You get a job that finds people who match a filter, pulls a verified work email for each, and hands the address to the tool that sends your message. It needs two LeadOcean calls and no seat licence. The send step can be Gmail, SMTP or your sequencer.

How it works

1. Trigger. Run the job on a schedule (cron, a workflow tool timer or a CI job). Once a day is enough for most lists.

1. Search. Call POST /v1/people/search with your filters. Add emailStatus: ["verified"] so you only pay for people you can mail. Page with cursor.

1. Enrich. For each person_id, call POST /v1/people/enrich with reveal_email: true. A person with nothing on file returns a 404 and costs nothing.

1. Send. Pass the address and name to your sender. Skip anyone already contacted. LeadOcean does not send mail and has no sequencer.

Size the list first, then start small. Run the job on 25 rows, read the messages in your sender's drafts and only then switch on live sending. A bad filter costs records, and a bad template costs your sender's reputation. Send in batches rather than one burst, and log each address you have mailed so a rerun never repeats a message. To size the list for free, send the same search with count=true as a query parameter and limit 1.

Configuration

curl -s https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jobLevel": ["VP"],
    "jobFunction": ["Sales & Business Development"],
    "country": ["US"],
    "emailStatus": ["verified"],
    "limit": 25
  }'

curl -s https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "PERSON_ID_FROM_SEARCH", "reveal_email": true}'

The search body is flat JSON. Filters such as country and jobLevel are arrays of strings, and limit runs from 1 to 100. Enum values are exact strings. Look them up with GET /v1/enums before you change a filter. Send the key in the x-api-key header.

Keep the two calls in separate steps. Search is metered at one record per person returned, and enrich is a second record, so a failed send never forces you to search again. Store the person_id and the revealed address, and retry only the send.

Field mapping

Cost at 10,000 rows

Free cannot finish this job. It holds 1,000 records for life, and search plus enrich spends two records per person, so it covers about 500 rows. Use it to test.

At 10,000 rows, use Solo at $97 a month. Solo allows 10k enrichments every 5 hours and 100k search records every 5 hours, so the run fits in one window. There are no credits and no overage invoice.

Your sender has its own cost and daily cap. Read them in the sender's own docs before you schedule 10,000 sends. LeadOcean plans are on /pricing.

Troubleshooting

FAQ