Apify logo

Get LinkedIn Profile Detail (Apify)

Apify → Get LinkedIn Profile Detail (Apify)

POST/v1/apify-linkedin-profile-detail
texau__apify-linkedin-profile-detailenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/apify-linkedin-profile-detail
{
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "full_name": "sample",
    "first_name": "sample",
    "last_name": "sample",
    "headline": "sample",
    "about": "sample",
    "profile_url": "https://acme.com",
    "profile_picture_url": "https://acme.com",
    "location_city": "sample",
    "location_country": 1,
    "location_full": "sample",
    "current_company": "sample",
    "current_company_url": "https://acme.com",
    "top_skill": "sample",
    "connection_count": 1,
    "follower_count": 1,
    "is_creator": true,
    "is_influencer": true,
    "is_premium": true,
    "open_to_work": true,
    "email": "[email protected]"
  }
}

Retrieves detailed LinkedIn profile data including work experience, education, and certifications.

Install

Add get linkedin profile detail (apify) 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__apify-linkedin-profile-detail

When to use this.

The "Get LinkedIn Profile Detail" action, powered by Apify, enables users to retrieve comprehensive LinkedIn profile information, facilitating data enrichment for various applications. By providing a public LinkedIn profile URL as the input parameter, users can access detailed outputs such as full name, job title, current company, location, and more. The action returns essential data fields, including fullName, jobTitle, companyName, and email, among others, allowing for in-depth analysis of professional profiles. This functionality is particularly useful for recruiters, marketers, and businesses seeking to enhance their databases with accurate LinkedIn information, identify potential candidates, or analyze industry trends. The action falls under the enrichment category, making it a valuable tool for data-driven decision-making.

Try it

Run a sample request.

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

Get LinkedIn Profile Detail (Apify)

Try it

Public LinkedIn profile URL to scrape details for.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • full_name
    Full Name
    string
  • first_name
    First Name
    string
  • last_name
    Last Name
    string
  • headline
    Headline
    text
  • about
    About
    nullabletext
  • profile_url
    Profile Url
    string
  • profile_picture_url
    Profile Picture Url
    nullablestring
  • location_city
    Location City
    nullablestring
  • location_country
    Location Country
    nullablestring
  • location_full
    Location Full
    string
  • current_company
    Current Company
    string
  • current_company_url
    Current Company Url
    string
  • top_skill
    Top Skill
    nullablearray
  • connection_count
    Connection Count
    nullablenumber
  • follower_count
    Follower Count
    nullablenumber
  • is_creator
    Is Creator
    nullableboolean
  • is_influencer
    Is Influencer
    nullableboolean
  • is_premium
    Is Premium
    nullableboolean
  • open_to_work
    Open To Work
    nullableboolean
  • email
    Email
    string

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/apify-linkedin-profile-detail. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/apify-linkedin-profile-detail
curl -X POST 'https://v3-api.texau.com/api/v1/apify-linkedin-profile-detail' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "full_name": "sample",
    "first_name": "sample",
    "last_name": "sample",
    "headline": "sample",
    "about": "sample",
    "profile_url": "https://acme.com",
    "profile_picture_url": "https://acme.com",
    "location_city": "sample",
    "location_country": 1,
    "location_full": "sample",
    "current_company": "sample",
    "current_company_url": "https://acme.com",
    "top_skill": "sample",
    "connection_count": 1,
    "follower_count": 1,
    "is_creator": true,
    "is_influencer": true,
    "is_premium": true,
    "open_to_work": true,
    "email": "[email protected]"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get LinkedIn Profile Detail (Apify)→Search LinkedIn Sales Navigator People (Apify)→Search LinkedIn Profiles (Apify)

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 → get linkedin profile detail (apify) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get LinkedIn Profile Detail (Apify)Apify 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 limit30 / 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.

Light tier

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

Related

More Apify actions.

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__apify-...` 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 Get LinkedIn Profile Detail (Apify) in 60 seconds.

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

Start free →Read the API docs