Apollo logo

Find Email using Linkedin Url (Apollo)

ApolloFind Email using Linkedin Url (Apollo)

POST/v1/apollo-enrich-person-using-linkedin
texau__apollo-enrich-person-using-linkedinenrichment
cURL · api.texau.app
84ms
POST/v1/apollo-enrich-person-using-linkedin
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "person_id": "rec_4f3a91",
    "first_name": "sample",
    "last_name": "sample",
    "unique_name": "sample",
    "linkedin_url": "https://acme.com",
    "title": "sample",
    "headline": "sample",
    "photo_url": "https://acme.com",
    "email": "[email protected]",
    "city": "sample",
    "state": "sample",
    "country": 1,
    "formatted_address": "sample",
    "time_zone": "sample",
    "seniority": "sample",
    "org_id": "rec_4f3a91",
    "org_name": "sample",
    "org_website_url": "https://acme.com",
    "org_linkedin_url": "https://acme.com",
    "org_domain": "https://acme.com",
    "org_mobile_number": "sample",
    "org_industry": "sample",
    "org_employee": 1,
    "org_founded_year": 1,
    "org_description": "sample",
    "org_logo_url": "https://acme.com",
    "waterfall_status": "valid",
    "waterfall_message": "sample",
    "request_id": "rec_4f3a91"
  }
}

Find Email using Linkedin Url (Apollo)

Install

Add find email using linkedin url (apollo) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__apollo-enrich-person-using-linkedin

When to use this.

The "apollo-enrich-person-using-linkedin" action is designed to enhance user profiles by extracting comprehensive contact and professional information from a provided LinkedIn URL. By inputting the LinkedIn URL (text), users can retrieve a wealth of data, including the individual's first name, last name, email address, job title, and organization details. The output fields encompass various semantic types such as ID, text, email, and URL, providing essential insights like formatted address, time zone, and organizational metrics. This action is particularly useful for sales teams, recruiters, and marketing professionals seeking to enrich their databases with accurate contact information and professional profiles, thereby facilitating targeted outreach and relationship building. As part of the enrichment category, it streamlines the process of gathering valuable data from LinkedIn, making it an indispensable tool for enhancing lead generation and networking efforts.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Find Email using Linkedin Url (Apollo)

Try it

LinkedIn Url

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • person_id
    Person Id
    nullabletext
  • first_name
    First Name
    text
  • last_name
    Last Name
    text
  • unique_name
    Unique Name
    text
  • linkedin_url
    Linkedin Url
    text
  • title
    Title
    text
  • headline
    Headline
    nullabletext
  • photo_url
    Photo Url
    nullabletext
  • email
    Email
    text
  • city
    City
    nullabletext
  • state
    State
    nullabletext
  • country
    Country
    nullabletext
  • formatted_address
    Formatted Address
    nullabletext
  • time_zone
    Time Zone
    nullabletext
  • seniority
    Seniority
    nullabletext
  • org_id
    Org Id
    nullabletext
  • org_name
    Org Name
    text
  • org_website_url
    Org Website Url
    text
  • org_linkedin_url
    Org Linkedin Url
    nullabletext
  • org_domain
    Org Domain
    text
  • org_mobile_number
    Org Mobile Number
    nullabletext
  • org_industry
    Org Industry
    text
  • org_employee
    Org Employee
    nullablenumber
  • org_founded_year
    Org Founded Year
    nullablenumber
  • org_description
    Org Description
    nullabletext
  • org_logo_url
    Org Logo Url
    nullabletext
  • waterfall_status
    Waterfall Status
    nullabletext
  • waterfall_message
    Waterfall Message
    nullabletext
  • request_id
    Request Id
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/apollo-enrich-person-using-linkedin. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/apollo-enrich-person-using-linkedin
curl -X POST 'https://v3-api.texau.com/api/v1/apollo-enrich-person-using-linkedin' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "person_id": "rec_4f3a91",
    "first_name": "sample",
    "last_name": "sample",
    "unique_name": "sample",
    "linkedin_url": "https://acme.com",
    "title": "sample",
    "headline": "sample",
    "photo_url": "https://acme.com",
    "email": "[email protected]",
    "city": "sample",
    "state": "sample",
    "country": 1,
    "formatted_address": "sample",
    "time_zone": "sample",
    "seniority": "sample",
    "org_id": "rec_4f3a91",
    "org_name": "sample",
    "org_website_url": "https://acme.com",
    "org_linkedin_url": "https://acme.com",
    "org_domain": "https://acme.com",
    "org_mobile_number": "sample",
    "org_industry": "sample",
    "org_employee": 1,
    "org_founded_year": 1,
    "org_description": "sample",
    "org_logo_url": "https://acme.com",
    "waterfall_status": "valid",
    "waterfall_message": "sample",
    "request_id": "rec_4f3a91"
  }
}

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → find email using linkedin url (apollo) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Find Email using Linkedin Url (Apollo)Apollo action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit60 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Standard tier

Pricing tier on /pricing. Per-action credit cost is private.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__apollo-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Find Email using Linkedin Url (Apollo) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.