B2b logo

Export LinkedIn Post Likers

TexAu → Export LinkedIn Post Likers

POST/v1/b2b-enrichment-linkedin-post-likers
texau__b2b-enrichment-linkedin-post-likersenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/b2b-enrichment-linkedin-post-likers
{
  "post_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "reaction_type": "sample",
    "reactor_entity_urn": "sample",
    "reactor_first_name": "sample",
    "reactor_last_name": "sample",
    "reactor_headline": "sample",
    "reactor_profile_id": "rec_4f3a91",
    "reactor_profile_picture": "sample",
    "reactor_profile_background": "sample",
    "reactor_object_urn": 1,
    "reactor_profile_type": "sample"
  }
}

Retrieves a list of LinkedIn users who liked a specific post with their profile details.

Install

Add export linkedin post likers 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-linkedin-post-likers

When to use this.

Retrieves a list of LinkedIn users who liked a specific post with their profile details.

Try it

Run a sample request.

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

Export LinkedIn Post Likers

Try it

The LinkedIn post url

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • reaction_type
    Reaction Type
    string
  • reactor_entity_urn
    Reactor Entity Urn
    nullablestring
  • reactor_first_name
    Reactor First Name
    string
  • reactor_last_name
    Reactor Last Name
    string
  • reactor_headline
    Reactor Headline
    nullablestring
  • reactor_profile_id
    Reactor Profile Id
    string
  • reactor_profile_picture
    Reactor Profile Picture
    nullablestring
  • reactor_profile_background
    Reactor Profile Background
    nullablestring
  • reactor_object_urn
    Reactor Object Urn
    nullablenumber
  • reactor_profile_type
    Reactor Profile Type
    nullablestring

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/b2b-enrichment-linkedin-post-likers. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/b2b-enrichment-linkedin-post-likers
curl -X POST 'https://v3-api.texau.com/api/v1/b2b-enrichment-linkedin-post-likers' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"post_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "reaction_type": "sample",
    "reactor_entity_urn": "sample",
    "reactor_first_name": "sample",
    "reactor_last_name": "sample",
    "reactor_headline": "sample",
    "reactor_profile_id": "rec_4f3a91",
    "reactor_profile_picture": "sample",
    "reactor_profile_background": "sample",
    "reactor_object_urn": 1,
    "reactor_profile_type": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Export LinkedIn Post Likers→Get LinkedIn Post Details→Export LinkedIn Post Comments

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Export LinkedIn Post LikersTexAu 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.

Heavy tier

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

Related

More TexAu 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__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 Export LinkedIn Post Likers in 60 seconds.

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

Start free →Read the API docs