Sign in
Reverse lookup

Find person by email (single)

Given an email address, find the person's LinkedIn profile and personal details. If the person's name, company, or other identifiers are also available, use the Kitchen Sink endpoint instead — it accepts all available signals and produces better matches. To avoid 429 errors, space requests evenly (such as 1/60th the rate limit per second) rather than bursting them all at once.

Billing: you are charged for one lookup operation per request — a hit bills emailToLinkedinUrl, a completed miss that queried providers bills emailToLinkedinMiss. Cached not-found results and rejected inputs are not billed.

<span>⚡ <strong>Rate limit:</strong> 3500 requests per 1 minute</span>

<span>💰 <strong>Cost:</strong> 2 credits per email lookup <span title="Pricing shown is default pricing. Actual pricing may vary.">ⓘ</span></span>

<span>⏱ <strong>Recommended timeout:</strong> 1 minute <span title="Recommended timeout: set your HTTP client timeout to at least 1 minute for this endpoint.">ⓘ</span></span>

post/v1/email-to-person/single

Request body

apiKeystring required

Your Fiber API key

emailstring email required

The email address of a person whose LinkedIn profile you want to find.

Response

Default Response

advicestring[] nullable

Tips, recommendations, and suggestions for using this API effectively.

Changes

Changed in 3 of the 12 revisions of this API.218

  • f8a78c729da914See the full diff
    • ●

      removed the optional property ///// from the response with the status

      response-optional-property-removed

    • ○

      added the optional property ////// to the response with the status

      response-optional-property-added

    • ○

      added the optional property ////// to the response with the status

      response-optional-property-added

    • ○

      added the optional property ////// to the response with the status

      response-optional-property-added

    • ○

      added the optional property ////// to the response with the status

      response-optional-property-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 4002aa81d4fb21See the full diff
    • ▲

      the response property became nullable for the status

      response-property-became-nullable

    • ▲

      the response property became optional for the status

      response-property-became-optional

    • ○

      the response's property default value was removed for the status

      response-property-default-value-removed

  • fda5277ff34f3See the full diff
    • ○

      api tag Reverse lookup added

      api-tag-added

    • ○

      api tag Email lookup removed

      api-tag-removed

    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog