---
title: "linkedin.status"
method: GET
path: "/v1/linkedin/status"
tags: ["linkedin"]
---

# linkedin.status

`GET /v1/linkedin/status`

## Request

- Base URL: `https://api.selda.ai`
- URL: `https://api.selda.ai/v1/linkedin/status`
- Auth: HTTP bearer

Is LinkedIn connected to this workspace, the account's state, today's invite and message limits (used and remaining), and whether plan and mode allow sending. Read only.

Dispatched to `linkedin.status` on `POST /mcp/query`. This route is a different URL for the same call: the request is answered by the same dispatcher, with the same authentication, the same scope check, the same organisation scoping and the same refusals.

- Scope: `read`
- A free sandbox key may call it
- MCP tools that wrap the same function: `selda_linkedin_status`
- Filled in from your API key, never sent by you: `orgId`

## Query parameters

- `projectId` string, required

## Response `200`

The call succeeded.

- object
  - `value` unknown, required
  - `request_id` string, required: Echoed in the `X-Request-Id` header.

## Other responses

- `400`: Unknown route, or arguments the validator refused.
- `401`: Missing, expired or revoked key.
- `403`: The key lacks the scope, the plan entitlement, or is a sandbox key on a live-only function.
- `429`: Rate limited. Wait for the next minute window and retry.
- `500`: The function threw. The message says what, without leaking internals.

---

[API](https://skmtc.dev/selda/apis/selda-api.md) · [All operations](https://skmtc.dev/selda/apis/selda-api/llms.txt) · [OpenAPI document](https://skmtc.dev/selda/apis/selda-api/revisions/f0b115a94c0f?raw)