Skip to main content
Recipe prompt
Phone number API flow for dialers: a profile URL goes into Forager and a phone number comes backPhone number API flow for dialers: a profile URL goes into Forager and a phone number comes back

What you’ll build

A small backend endpoint for your dialer. A rep opens a prospect, the dialer sends the prospect’s LinkedIn profile URL to your server, and your server returns the phone numbers Forager has for that person.
The response lists phone_number values and nothing else. The API reference does not document a line-type field, so this recipe does not promise mobile-only results.

Steps

1

Get your credentials

Create an API key and note your Account ID. See Authentication. Export them on your server as FORAGER_API_KEY and FORAGER_ACCOUNT_ID.
2

Extract the LinkedIn public identifier

The lookup takes linkedin_public_identifier, the slug in linkedin.com/in/<slug>/. Parse it from the profile URL.
3

Call the phone numbers lookup

Send a POST to Phone numbers lookup.
Example response (illustrative values)
4

Show the numbers and report the outcome

Return the numbers to the dialer. After the call, you can tell Forager whether a number was connected or disconnected with Submit phone-number verification feedback. It takes phone_number and contact_status.

Handle the edge cases

  • Not found. An empty list means no numbers. Show “no number found” and let the rep skip the call.
  • 403. The key is missing, invalid or not allowed. Check FORAGER_API_KEY and FORAGER_ACCOUNT_ID, and do not retry.
  • 429. Back off and retry. See errors and rate limits.
  • Credits. A phone number lookup costs 15 credits per lookup. Cache results per person so a rep reopening a prospect does not spend again. See credit pricing.

Find phone numbers

The guide behind this recipe.

Phone numbers lookup

Request and response reference.

Enrich a contact

Get the full person record.
Last modified on October 28, 2026