Skip to main content
Choose the right Forager API endpoint: inputs such as a profile URL, email, phone or filters map to the endpoint that returns what you needChoose the right Forager API endpoint: inputs such as a profile URL, email, phone or filters map to the endpoint that returns what you need
Start from what you already have, then follow the row to the endpoint that returns what you need. Searching and counting first, then looking up contact details only for the people you keep, is usually the cheapest path.

​
You have a person

​
You have criteria, not a person

Search first, keep the people you need, then run contact lookups to save Forager API creditsSearch first, keep the people you need, then run contact lookups to save Forager API credits
Search filters such as industries, locations, skills, keywords and technologies take IDs, not free text. Get the IDs from the autocomplete endpoints first.

​
Typical flows

1

Build a prospect list

Resolve filter IDs with autocomplete, run People search, then look up a work email or phone number only for the people you keep. Guide: Search people by role.
2

Enrich a CRM contact

Start from the LinkedIn handle with Person lookup, or from an email with Reverse email lookup. Guide: Enrich a contact.
3

Enrich thousands of contacts

Use the bulk work email finder with a webhook_url instead of polling. Guide: Bulk work emails. For whole datasets, a data feed is usually cheaper than the API.
Costs come from API credits and pricing, which is the source of truth if the two ever differ.
Last modified on October 28, 2026