Dux-Soup LinkedIn Activity API

Name: Dux-Soup LinkedIn Activity API API
Brand: Dux-Soup LinkedIn Activity API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing AutomationapiKey1 EndpointsREST

For Agents

Queue LinkedIn automation commands (visit, connect, message, enroll, tag) for a Dux-Soup user account so prospecting actions run from external workflows instead of the browser.

Quickstart

Get started with Dux-Soup LinkedIn Activity API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"queue a LinkedIn action with Dux-Soup"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Dux-Soup LinkedIn Activity API API.

Queue a LinkedIn profile visit for a specific Dux-Soup user account

Send a connection request to a LinkedIn profile with an optional personalised message

Dispatch a direct message to an existing first-degree LinkedIn connection

Enroll a LinkedIn profile into a Dux-Soup drip campaign by campaign ID

GET STARTED

Start building with Dux-Soup LinkedIn Activity API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Dux-Soup LinkedIn Activity API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Dux-Soup LinkedIn Activity API, keeping it validated and agent-ready. The Dux-Soup LinkedIn Activity API lets Turbo and Cloud users trigger automated LinkedIn outreach from outside the browser by queueing remote commands such as visit, connect, message, enroll, tag, and untag. Each command is HMAC-signed and dispatched to a specific Dux-Soup user account, where the Dux-Soup browser extension picks up the queued action and executes it on LinkedIn. The API exposes a single queue endpoint and is designed for integrating LinkedIn prospecting steps into CRM workflows, drip sequences, and outbound campaigns.

Use Cases

Patterns agents use Dux-Soup LinkedIn Activity API API for, with concrete tasks.

★ CRM-Triggered LinkedIn Outreach

When a sales rep marks a contact as 'ready to engage' in the CRM, automatically queue a LinkedIn visit and connection request through Dux-Soup so the prospecting step runs without manual browser work. The Dux-Soup extension picks up the command from the queue and performs the action under the rep's logged-in LinkedIn session, keeping the outreach native to the user's account.

Queue a 'connect' command for LinkedIn profile https://www.linkedin.com/in/jane-doe with the message 'Hi Jane, saw your post on B2B sales - would love to connect' for Dux-Soup user 12345

Drip Campaign Enrollment

Push qualified leads from a lead-scoring pipeline directly into a Dux-Soup multi-step LinkedIn campaign. The 'enroll' command attaches a profile to a named campaign so visits, invites, follow-ups, and InMails are sequenced automatically by Dux-Soup over days or weeks, while the source system continues to score and route new leads.

Send a POST to /remote/control/{userId}/queue with command 'enroll', the prospect's LinkedIn URL, and the campaign ID for the 'Q3 Outbound SaaS' sequence

Tag-Based List Hygiene

Apply Dux-Soup tags to LinkedIn profiles based on external signals - intent data, email replies, deal stage - so segmentation lives alongside the contact in LinkedIn rather than only in the CRM. The 'tag' and 'untag' commands let an automation pipeline keep Dux-Soup's view of a prospect synchronised as their status changes.

Queue a 'tag' command adding the tag 'replied-positive' to LinkedIn profile https://www.linkedin.com/in/john-smith for Dux-Soup user 12345

Agent-Driven LinkedIn Workflows via Jentic

An AI agent orchestrating outbound sales tasks calls the Dux-Soup queue endpoint through Jentic to run the LinkedIn step of a multi-channel sequence. The agent searches Jentic for 'queue a LinkedIn action', loads the input schema for the queue endpoint, and executes the call with the chosen command and target profile - no Dux-Soup SDK or browser context required.

Use Jentic to search 'queue a LinkedIn action with Dux-Soup', load the queue operation, and execute a 'visit' command on a target LinkedIn profile

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for dux-soup linkedin activity api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/remote/control/{userId}/queue

Queue a LinkedIn activity command for a Dux-Soup user

POST

/remote/control/{userId}/queue

Queue a LinkedIn activity command for a Dux-Soup user

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Dux-Soup API key and HMAC secret are stored encrypted in the Jentic vault. Agents receive a scoped execution token; the raw key and secret never enter the agent's context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'queue a LinkedIn connection request') and Jentic returns the Dux-Soup queue operation with its input schema, so the agent can call it without browsing Dux-Soup documentation.

Time to first call

Direct Dux-Soup integration: 1-2 days to wire up HMAC signing, error handling, and per-user routing. Through Jentic: under 30 minutes - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Dynosend API

Email and transactional messaging - pair with Dux-Soup to run LinkedIn plus email touches in one outbound sequence

Choose Dynosend when the next step in the outreach sequence is an email rather than a LinkedIn action

Complementary

E-goi Marketing API

Multi-channel marketing automation (email, SMS, push) that complements Dux-Soup's LinkedIn-only scope

Use E-goi for SMS, email, and push channels, and Dux-Soup for the LinkedIn step of the same sequence

Complementary

DynaPictures API

Generate personalised images for LinkedIn messages or InMails dispatched via Dux-Soup

Pick DynaPictures to render a personalised banner before queueing a Dux-Soup connect or message command

FAQs

Specific to using Dux-Soup LinkedIn Activity API API through Jentic.

Why is there no official OpenAPI spec for Dux-Soup LinkedIn Activity API?

Dux-Soup does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Dux-Soup LinkedIn Activity API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Dux-Soup LinkedIn Activity API use?

The API uses an API key passed in the X-API-Key header, and Dux-Soup additionally requires HMAC-signed payloads on the queue request. Through Jentic, the API key is held in the encrypted vault and never enters the agent context - the agent receives a scoped execution token instead.

Can I send a LinkedIn message with the Dux-Soup LinkedIn Activity API?

Yes. Send a POST to /remote/control/{userId}/queue with command 'message', the target profile URL, and the message body. Dux-Soup will only deliver messages to first-degree connections - for non-connections you must queue a 'connect' command first with the message attached to the invite.

What are the rate limits for the Dux-Soup LinkedIn Activity API?

The OpenAPI spec does not declare a numeric rate limit. In practice the limiting factor is LinkedIn's own daily activity caps, which Dux-Soup enforces locally per user account through Turbo/Cloud throttling settings rather than at the queue endpoint.

How do I queue a LinkedIn connection request through Jentic?

Run pip install jentic, search for 'queue a LinkedIn connection request with Dux-Soup', load the operation for POST /remote/control/{userId}/queue, then execute it with command 'connect', the target LinkedIn URL, an optional message, and the Dux-Soup user ID. Jentic injects the API key and HMAC signature.

Is the Dux-Soup LinkedIn Activity API free?

API access requires a Dux-Soup Turbo or Cloud subscription - the free tier of Dux-Soup does not expose remote queueing. Pricing is per LinkedIn user account per month and is set on the Dux-Soup website rather than in the spec.