B2b logo

Enrich Contact

TexAuEnrich Contact

POST/v1/b2b-enrichment-enrich-contact
texau__b2b-enrichment-enrich-contactenrichment
cURL · api.texau.app
84ms
POST/v1/b2b-enrichment-enrich-contact
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "url": "https://acme.com",
    "identifier": "sample",
    "entity_urn": "sample",
    "object_urn": 1,
    "first_name": "sample",
    "last_name": "sample",
    "middle_name": "sample",
    "headline": "sample",
    "picture": "sample",
    "summary": "sample",
    "industry": "sample",
    "open_to_work": true,
    "premium": true,
    "location_country": 1,
    "location_city": "sample",
    "location_state": "sample",
    "location_full": "sample",
    "current_company_name": "sample",
    "current_company_domain": "https://acme.com",
    "current_company_logo": "sample",
    "current_company_linkedin_url": "https://acme.com",
    "current_job_title": "sample",
    "current_employment_type": "sample",
    "current_job_start_date": "sample",
    "current_job_end_date": "sample"
  }
}

Extracts contact details from a LinkedIn profile including email, phone, job title, and company.

Install

Add enrich contact 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__b2b-enrichment-enrich-contact

When to use this.

The "Enrich Contact" action is designed to extract comprehensive contact details from a LinkedIn profile, including essential information such as email, phone number, job title, and company affiliation. By providing a LinkedIn profile URL as the key input parameter, users can seamlessly retrieve enriched data about the individual, including their first name, last name, current company name, and location details. The output fields encompass a wide range of semantic types, such as linkedinProfileUrl, jobTitle, companyDomain, and more, allowing for detailed insights into the contact's professional background. This action is particularly useful for businesses seeking to enhance their B2B marketing efforts, improve lead generation, and build robust customer databases. As part of the enrichment category, it serves as a vital tool for sales teams, recruiters, and marketing professionals aiming to gain a deeper understanding of potential clients or candidates.

Try it

Run a sample request.

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

Enrich Contact

Try it

LinkedIn profile URL (e.g., https://www.linkedin.com/in/rajeevsahu21)

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • url
    Url
    text
  • identifier
    Identifier
    nullabletext
  • entity_urn
    Entity Urn
    nullabletext
  • object_urn
    Object Urn
    nullablenumber
  • first_name
    First Name
    text
  • last_name
    Last Name
    text
  • middle_name
    Middle Name
    nullabletext
  • headline
    Headline
    text
  • picture
    Picture
    text
  • summary
    Summary
    text
  • industry
    Industry
    text
  • open_to_work
    Open To Work
    nullableboolean
  • premium
    Premium
    nullableboolean
  • location_country
    Location Country
    text
  • location_city
    Location City
    nullabletext
  • location_state
    Location State
    nullabletext
  • location_full
    Location Full
    nullabletext
  • current_company_name
    Current Company Name
    text
  • current_company_domain
    Current Company Domain
    text
  • current_company_logo
    Current Company Logo
    nullabletext
  • current_company_linkedin_url
    Current Company Linkedin Url
    text
  • current_job_title
    Current Job Title
    text
  • current_employment_type
    Current Employment Type
    nullabletext
  • current_job_start_date
    Current Job Start Date
    nullablestring
  • current_job_end_date
    Current Job End Date
    nullablestring

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/b2b-enrichment-enrich-contact. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/b2b-enrichment-enrich-contact
curl -X POST 'https://v3-api.texau.com/api/v1/b2b-enrichment-enrich-contact' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "url": "https://acme.com",
    "identifier": "sample",
    "entity_urn": "sample",
    "object_urn": 1,
    "first_name": "sample",
    "last_name": "sample",
    "middle_name": "sample",
    "headline": "sample",
    "picture": "sample",
    "summary": "sample",
    "industry": "sample",
    "open_to_work": true,
    "premium": true,
    "location_country": 1,
    "location_city": "sample",
    "location_state": "sample",
    "location_full": "sample",
    "current_company_name": "sample",
    "current_company_domain": "https://acme.com",
    "current_company_logo": "sample",
    "current_company_linkedin_url": "https://acme.com",
    "current_job_title": "sample",
    "current_employment_type": "sample",
    "current_job_start_date": "sample",
    "current_job_end_date": "sample"
  }
}

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 → enrich contact → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Enrich ContactTexAu 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__texau-...` 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 Enrich Contact in 60 seconds.

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