Skip to main content
In about 5 minutes you’ll look up the phone numbers for one person from their LinkedIn public identifier, the part of a profile URL after /in/.
A LinkedIn profile URL goes into Forager and phone numbers come backA LinkedIn profile URL goes into Forager and phone numbers come back
Using a coding agent? Paste this instead and it will do the steps for you:
Setup prompt
1

Get your API key and Account ID

Create a free account at app.forager.ai. Then:
  • Create a key on the API page.
  • Copy your Account ID from My Account.
Set both in your terminal:
Keep the key server-side. Don’t commit it or put it in browser code. See authentication.
2

Look up phone numbers

Send a POST to the phone number lookup with a LinkedIn public identifier. You can send a Forager person_id instead.
Each phone number lookup uses 15 credits. See credits and pricing.
3

Read the response

The response is a list of phone numbers. Each item has a phone_number field.
Example response (illustrative values)
If the key is missing or wrong, you get a 403:See API errors and rate limits for the errors documented so far and their response bodies.

Go deeper in your language

The cURL, Python and Node.js quickstarts repeat these steps with a small client that handles 403 and 429, then submit and poll an asynchronous work email lookup.

Build your next request

Pick an endpoint and fill in the parameters to get the matching cURL, Python or JavaScript. The samples read FORAGER_API_KEY and FORAGER_ACCOUNT_ID from your environment; nothing is sent from this page.

Next steps

Choose the right endpoint

Match what you have to what you need, with the cost of each call.

Recipes

End-to-end builds for dialers, CRMs, recruiting and data teams.

Try it in the API reference

Send the same request from your browser.

Postman collection

Every operation, ready to import. Set the apiKey and accountId variables.
Last modified on November 1, 2026