Contact details

Start exhaustive contact details reveal

Changed on

Maximum-coverage contact reveal — runs multiple enrichment sources in parallel for the highest yield. This is our SLOWEST endpoint by design: expect to wait roughly 2–3 minutes for results. This is an asynchronous operation — call it to start the task, then poll /contact-details/exhaustive/poll with the returned task ID every 15–30 seconds. Do NOT use this endpoint in time-sensitive flows. If speed matters, use /contact-details/turbo/sync (fastest), /contact-details/single (balanced), or /contact-details/lite (cheapest) instead — exhaustive is for when maximum coverage is worth the wait.

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

<span>💰 <strong>Cost:</strong> Pay only for the data you request (exhaustive mode):<br />• 12 credits for all phone numbers AND all emails<br />• 5 credits for work email only<br />• 5 credits for personal email only<br />• 4 credits for phone only<br />• 9 credits for all emails <span title="Pricing shown is default pricing. Actual pricing may vary. Credits are charged upfront for the requested exhaustive bundle. Undelivered data is refunded per operation after the reveal completes, so partial reveals only bill for delivered data.">ⓘ</span></span>

post/v1/contact-details/exhaustive/start

Request

  • Base URL
    https://api.fiber.ai
  • URL
    https://api.fiber.ai/v1/contact-details/exhaustive/start
  • Auth
    none declared

Request body

apiKeystring required

Your Fiber API key

linkedinUrlstring required

The person's LinkedIn identifier. Accepts a full LinkedIn profile URL (e.g. 'https://www.linkedin.com/in/williamhgates/'), a bare slug (e.g. 'williamhgates'), a Sales Navigator URN (e.g. 'ACwAAA-001MBbIvJon'), or a numeric LinkedIn user ID (e.g. '443105112').

Response

Default Response

advicestring[] nullable

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

Changes

    • info

      added the non-success response with the status

    • breaking

      the response property became nullable for the status

    • breaking

      the response property became optional for the status

    • info

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