LinkedIn's Social Selling Index for this sender: a 0-100 score built from four 0-25 pillars (professional brand, finding the right people, engaging with insights, building relationships), plus where the profile ranks against its industry and its network.
The score is cached on the account and refetched once it goes stale (LinkedIn recomputes it daily at most). Pass refresh=true to force a live read. unavailable: true means LinkedIn does not expose a score for this account's session, which is a state rather than an error.
Authorization
bearerAuth An API key created under Settings → API & Webhooks.
In: header
Path Parameters
Query Parameters
Force a live read instead of using the cached score.
falseResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/accounts/string/ssi"{ "data": { "score": 0, "brand": 0, "people": 0, "insights": 0, "relationships": 0, "industryTop": 0, "networkTop": 0, "industryAverage": 0, "networkAverage": 0, "industryName": "string", "unavailable": true, "syncedAt": "2019-08-24T14:15:22Z" }}Get the pending sign-in challenge GET
The verification step this sender is waiting on, or `null` when there is none. `type` is 2FA, OTP, IN_APP_VALIDATION, PHONE_REGISTER or CAPTCHA; `input` says what answers it (`code`, `phone`, `none` when it is approved in the LinkedIn mobile app, `hosted` for a captcha that has to be solved on LinkedIn's own page); `expiresAt` is when LinkedIn drops the attempt, five minutes after it asked. IN_APP_VALIDATION and CAPTCHA are completed outside the API, so poll this endpoint (or listen for account.status_changed) — it re-reads the live session and clears the challenge as soon as the sender is up.
Sender performance GET
How this sender has performed over the last `days`: connection requests, acceptances, messages, replies and interested leads with period-over-period deltas, a daily activity series, all-time totals and rates, the per-campaign split, direct (non-campaign) action counts, and how much headroom is left against its daily and rolling-weekly caps. Campaign sends and direct API sends are both counted. Daily series buckets are calendar days on the server's clock; the daily caps themselves reset at 00:00 UTC.