API Reference/Endpoints

Call the LinkedIn API directly

ANY/api/linkedin/gateway/{...path}

A pass-through proxy over the full LinkedIn engine underneath Warmably — messaging, users, posts, emails, calendars — beyond the few actions with their own bespoke endpoints above. Forward any GET, POST, PUT, PATCH or DELETE to it under your own account's scope. The example alongside is a real one — looking up a public profile, including its connection degree to your account.

Authentication

Send your personal API key as a bearer token. A missing, malformed or revoked key returns 401.

Resolving account_id

Every call must resolve to an account you own, checked in this order:

·1. ?account_id=... query param — what most GET/list calls use.·2. An account_id field in a JSON body — most POST/PATCH calls.·3. An /accounts/{id}/... path segment — the Accounts category itself.

Blocked paths

A handful of endpoints have no per-account scoping, or would bypass bookkeeping this API relies on — these return 404 here regardless of your key:

·GET /accounts. Would list every account on the workspace, not just yours.·POST /accounts. Account creation — use Connect a LinkedIn account instead.·POST /accounts/checkpoint. Use Submit a checkpoint code instead.·/webhooks. Workspace-level configuration, not a per-account action.

Only JSON request bodies are forwarded. A few messaging endpoints that take file uploads (attachments, voice or video messages) aren't reachable through this route yet.

Errors

·400 Bad Request. The request didn't resolve to an account_id.·401 Unauthorized. The key is missing, malformed or has been rotated.·403 Forbidden. The account_id doesn't belong to this key.·404 Not Found. The path is blocked (see above), or doesn't exist upstream.·Anything else is passed through unchanged from the LinkedIn engine's own response.