LinkedIn messaging API: message connections and InMail from your account

linkedin.message

live

Message a connection from your account, reply in an existing thread, or send an InMail (Premium or open profiles). You are the sender of record.

live coverage

Unipile: all inputs

✓ marks a combination proven with a real provider call. Others are wired and unit-tested; their first live run verifies them.

Providers

Provider	Status
Unipile	live

Billing

Unit: per_message · unmatched results billed: no
Priced per message sent; a refused send bills nothing.

The exact quote is returned by /v1/inspect before every call and held with headroom on execution. The quote is the price floor: if the provider's actual cost overruns it, the run bills the overrun at the same rate, never above the hold. The unused part of every hold is released.

Run it

curl https://api.jell.run/v1/run \
  -H "Authorization: Bearer $JELL_API_KEY" \
  -d '{
    "capability": "linkedin.message",
    "input": { "text": "..." },
    "routing": {"provider": "auto"}
  }'

Input schema

{
  "properties": {
    "account_id": {
      "description": "The account name (or id) from linkedin.accounts; optional when you have one account",
      "type": "string"
    },
    "chat_id": {
      "description": "From linkedin.messages: reply in that thread",
      "type": "string"
    },
    "inmail": {
      "default": false,
      "description": "Send as InMail (needs a subject)",
      "type": "boolean"
    },
    "profile_url": {
      "description": "Start a new conversation with this person",
      "type": "string"
    },
    "provider_id": {
      "type": "string"
    },
    "subject": {
      "type": "string"
    },
    "text": {
      "type": "string"
    }
  },
  "required": [
    "text"
  ],
  "type": "object"
}

Normalized output fields

chat_id · message_id