canonical: https://jentic.com/apis/dux-soup.com/dux-soup # Dux-Soup LinkedIn Activity API 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. ## For AI 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. ## Scope Does not scrape LinkedIn profile data, send LinkedIn ads, or run non-LinkedIn channels - use for queueing automated LinkedIn actions through a Dux-Soup user account only. ## Capabilities - 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 - Tag or untag LinkedIn profiles to drive segmented follow-up sequences - Sign queued commands with HMAC so the Dux-Soup extension authenticates each request ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | Method | Path | Description | | --- | --- | --- | | POST | `/remote/control/{userId}/queue` | Queue a LinkedIn activity command for a Dux-Soup user | ## Key resources - **Remote Control Queue** — Single endpoint that accepts LinkedIn commands (visit, connect, message, enroll, tag, untag) for a specific Dux-Soup user and queues them for the browser extension to execute ## Why Jentic - **Setup:** Wiring the Dux-Soup API by hand means handling its X-API-Key auth and targeting the right user account through the queue path yourself. Through Jentic you install once, import Dux-Soup from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Dux-Soup puts the user id in the URL path (`/remote/control/{userId}/queue`), so a rule can pin your agent to queueing actions for one Dux-Soup user account. Since this API exposes a single queue operation, that operation is the only thing the agent can call. - **Credential handling:** Your Dux-Soup API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'queue a LinkedIn connection request', and Jentic returns the Dux-Soup queue operation with its input schema so the agent calls the right endpoint without browsing the Dux-Soup documentation. ## Related APIs - **Dynosend API** — Email and transactional messaging - pair with Dux-Soup to run LinkedIn plus email touches in one outbound sequence - **E-goi Marketing API** — Multi-channel marketing automation (email, SMS, push) that complements Dux-Soup's LinkedIn-only scope - **DynaPictures API** — Generate personalised images for LinkedIn messages or InMails dispatched via Dux-Soup ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Dux-Soup LinkedIn Activity API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Dux-Soup API puts the account id in the URL path (`/remote/control/{userId}/queue`), so you can pin your agent to queueing actions for a single Dux-Soup user account. Since this API exposes only that one queue operation, it is the sole call your agent can make, and you control the stored API key that authorizes it.