Expandi

01

Setup

1. 01Generate a key and secret. In Expandi open Account Settings, select your default workspace, and under Expandi API keys click Generate. Copy both the key and the secret.
2. 02Connect Expandi. In the superagnt app open Integrations, pick Expandi, and paste the API key and the API secret. Both are required.

02

Things to know

• Workspace, companies, LinkedIn accounts. Companies group LinkedIn accounts inside a workspace, and one seat is one LinkedIn account (connection_expandi_workspace_read action subscriptions shows seats used and available).
• Almost everything hangs off one LinkedIn account. Start with connection_expandi_linkedin_accounts_read (action list) and pass an account's id as li_account_id to the campaign, lead, search, keyword and action tools.
• Messengers are leads. Expandi calls the relationship between a lead and a LinkedIn account a messenger. connection_expandi_campaigns_read action contacts returns each lead's contact, contact_status, conversation_status, invited_at, connected_at, last_datetime and has_new_messages, filtered by campaign_instance_id, search_filter_id or profile_link. Action messages returns one messenger's full thread.
• Campaigns are campaign instances, each with a type, a status, a contact count and a stats snapshot. Sequence step content is not readable through the API.
• Check the sender first. Nothing runs from a LinkedIn account that is disconnected or stuck on a login challenge. Action status on connection_expandi_linkedin_accounts_read shows status_code and any pending_challenge (a PIN, a phone number, an app confirmation or a new password), which only the account owner can clear, in the Expandi app.
• Actions run later. A scheduling call returns an action id at once, and Expandi performs the action from the real LinkedIn account inside the daily limits and working hours set for it in Expandi. Action action_status reports how it went (it cannot report a comment or a post): pass the action_id the scheduling call returned and its type (m for a message, cr for a connection request, and so on).
• No date filters. Lists page by number (page, from 1) and return count, next and previous. No list filters by date or sorts, so to find what changed, walk every page and compare updated.
• A wrong key or secret hangs. Expandi does not refuse a bad key or secret: it holds the request for 30 seconds or more. superagnt_ waits up to 60 seconds and never retries, so a timeout on a new connection usually means a mistyped key or secret. Expandi reports other failures as HTTP 400 with {"error": "..."}, which an MCP tool result carries in upstreamError.
• Some fields are objects. Expandi's own spec types several fields as strings that are really nested objects (contact, stats, placeholders). Read them as JSON.
• The blacklist is write-only. Entries cannot be read or removed through the API, and clear: true replaces the existing entries of the same field and match type.
• Rate limits. Expandi publishes no API rate limit. LinkedIn actions are paced by each account's limits in Expandi.
• The connection does not cover adding a LinkedIn account to Expandi (it takes the LinkedIn password and two-factor secret), the LinkedIn login flow and its challenges, or Expandi's legacy v1 routes.

03

Permissions

These defaults decide whether a superagnt_ agent runs a call or waits for a person (Permissions). Reads run without asking, and so do checking an action's status, creating an empty search and following keywords. Profile visits, changing a scheduled post, adding a contact to a search and blacklisting ask by default. Sending a LinkedIn message, connection request, email or open InMail, reacting to or commenting on a post, scheduling a post, adding, pausing or resuming a contact in a campaign, and every removal (a campaign contact, a search contact, a scheduled post, a followed keyword) always ask a person first.

04

Examples

List LinkedIn accounts

curl "https://api.superagnt.com/v1/connections/expandi/li_accounts/" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Read the leads in one campaign

curl "https://api.superagnt.com/v1/connections/expandi/li_accounts/$LI_ACCOUNT_ID/messengers/?campaign_instance_id=$CAMPAIGN_ID&page=1" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Read a lead's message thread

curl "https://api.superagnt.com/v1/connections/expandi/li_accounts/messengers/$MESSENGER_ID/messages/" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Add a contact to a campaign with placeholders

curl -X POST "https://api.superagnt.com/v1/connections/expandi/li_accounts/campaign_instances/$CAMPAIGN_ID/create_contact/" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "profile_link": "https://www.linkedin.com/in/ada-lovelace/",
    "placeholders": { "icebreaker": "Loved your talk on analytical engines" }
  }'

From an agent, adding a campaign contact always asks a person first: in an active campaign the sequence starts reaching out to the contact from the real LinkedIn account.

05

Receiving Expandi webhooks

Expandi webhooks can only be created in the Expandi app, per LinkedIn account (LinkedIn Settings → Webhooks), so agents cannot register them. To trigger an agent when a lead replies or accepts a connection request, create the webhook in Expandi and point it at a superagnt_ inbound webhook endpoint. Expandi signs nothing and does not retry, so use an endpoint URL nobody can guess.

06

Sync

An Expandi sync copies your LinkedIn accounts, campaigns, leads and their message threads into tables in your workspace database and keeps them fresh, so agents read local tables instead of paging Expandi on every run. Turn it on from the Sync panel on the Expandi connection page in the superagnt app. The panel previews the rows and webhook events against your plan before anything is created. How syncs work in general: Vendor sync.

How updates arrive. Expandi's API has no date filter and no ordering, so every pass re-reads the selected accounts' lists (hourly by default) and keeps only what changed. A campaign or lead that disappears at Expandi is marked deleted, and messages are re-read for each lead whose last activity moved. Webhook deliveries are stored whole in expandi_events and also make the sync re-read the leads, so a reply shows up without waiting for the hourly pass.

Set up the webhooks in Expandi. Expandi webhooks are created by hand, per LinkedIn account. Once the sync is on, the Sync panel shows its webhook URL in a copyable field next to these steps (on a workspace MCP connection, agnt_sync_status returns it as ingest_url):

1. 01Open the webhook settings. In Expandi, open a LinkedIn account's menu, then LinkedIn Settings, then Webhooks.
2. 02Pick an event. Click +Add a webhook and pick an event. We suggest Contact replied and Connection request accepted.
3. 03Paste the URL. Paste the URL from the Sync panel, click Send test, then Create webhook.
4. 04Repeat per account. Repeat for every LinkedIn account you want synced in real time. Accounts without the webhook still sync on the regular schedule.

Expandi signs nothing and never retries, and a webhook fires only for actions after it was created, so events missed while a webhook is off are lost from expandi_events (the leads and their threads still sync by polling). The Sync panel says so when deliveries stop while the leads keep changing. Turning the sync off and on again issues a new URL to paste.

Plans and scope.

• With a wrong key or secret, Expandi never answers. The sync's credential check waits 20 seconds, then says to check both and reconnect.
• One key spans every Expandi workspace and LinkedIn account its user can reach. The workspace and LinkedIn account filters narrow the sync.
• The sync only reads. It never sends a message, an invitation or any other LinkedIn action.
• Expandi publishes no rate limit, so the sync paces itself at 60 requests a minute.

What a Expandi sync copies

A sync copies these tables into your workspace database and keeps them fresh, so an agent reads local rows instead of calling Expandi on every run. Turn tables on and off from the Sync panel on the connection. Every table also carries _raw, _hash, _synced_at and _deleted_at. How syncs work: Vendor sync.

14 tools, one per resource and risk

MCP servers and agents on the grouped surface list Expandi as these tools. Each takes an action, and the ones that work across record types an object. Every operation also keeps its own per-operation name, in the next table, which works on every server. How grouping works: Grouped tools.

All 33 operations

Each operation is a REST path under https://api.superagnt.com/v1/connections/expandi and an MCP tool. The per-operation tool name is the one permissions, approvals and usage records use.

Related