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 caller’s resolved LinkedIn connection and has no sender-account selector. When no connection exists, action data is empty; when the provider integration is not configured, the empty response shape is returned.
For a connected account, actions is keyed by five policy actions: connect_request, message_in_network, message_out_network_inmail, visit_profile, and voice_message. Each action can include allowed, reason_code, retry_at, message, allowance, and windows. Allowance values and windows are current policy data, not a fixed quota promise. provider_cooldown is derived from those snapshots. InMail balance can be unavailable; the endpoint attempts a provider balance lookup.
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. |
