Get LinkedIn connection status

This page documents the canonical HTTP contract. Switch to the CLI example when you want the operator workflow.

This read endpoint is available to a developer API key with linkedin:read or an authenticated user session. It reports the LinkedIn integration selected for the caller in the request organization; it does not accept a sender-account selector.

The response includes connected, ready, status, reconnect_required, configured, account_id, feature, linkedin_api_mode, connection timestamps, connected_by, and per-surface surface_health. With no connection, it returns disconnected values rather than a not-found error. If the provider integration is not configured, status is still returned. For a connection, the handler may refresh stored health and mode metadata while building the response.

Errors

Status	Meaning
401	Invalid API key or missing auth.
403	Developer API key lacks linkedin:read scope.
400	Organization or user context is missing.

Example

bash

curl -X GET "https://app.autotouch.ai/api/integrations/linkedin/status" \
  -H "Authorization: Bearer stk_your_key_id.your_secret"

Response example

json

{
  "connected": true,
  "ready": true,
  "status": "ok",
  "reconnect_required": false,
  "configured": true,
  "account_id": "acc_abc123",
  "feature": "linkedin",
  "linkedin_api_mode": "sales_navigator",
  "connected_at": "2026-03-01T10:30:00Z",
  "updated_at": "2026-03-10T08:15:00Z",
  "connected_by": "user_abc123",
  "surface_health": {
    "linkedin_core": { "status": "ok", "reconnect_required": false, "message": "LinkedIn messaging, profile lookup, and invitations are connected." },
    "sales_navigator_search": { "status": "ok", "reconnect_required": false, "message": "Sales Navigator search is connected." },
    "inmail": { "status": "unknown", "reconnect_required": false, "message": "InMail availability depends on subscription credits." }
  }
}