---
title: "Send Committee Linkedin Invite"
method: POST
path: "/desk/accounts/{account_id}/committee/{contact_id}/linkedin-invite"
tags: ["Desk"]
---

# Send Committee Linkedin Invite

`POST /desk/accounts/{account_id}/committee/{contact_id}/linkedin-invite`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/desk/accounts/{account_id}/committee/{contact_id}/linkedin-invite`
- Auth: HTTP bearer

REACHES A REAL PERSON on LinkedIn, from the rep's own account.

Costs no credits, and that is not the point: a connection request arrives
in someone's notifications under a named human's identity and CANNOT BE
WITHDRAWN. That is why it is tiered alongside the sends rather than with
the writes.

The sender is the rep's OWN claimed LinkedIn account, resolved strictly -
it fails closed rather than falling back to whichever account the org
connected first. Claim one with `PUT /desk/linkedin-sender`.

409 on every refusal, with nothing queued: no sender picked, the account is
not connected, the person is not on this committee, or an invite is already
queued for them.

## Path parameters

- `account_id` integer, required: The account's mashup company id (`cb_account_plans.account_id`).
- `contact_id` integer, required: The committee member to invite.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- CommitteeLinkedInInviteRequest: The optional note on a LinkedIn connection request. 300 characters is LinkedIn's own cap, not a display limit.
  - `note` string, nullable: Optional invite note. Capped by LinkedIn at 300 characters.

## Response `200`

Successful Response

- ApiResponseAccountPlanPayload
  - `data` AccountPlanPayload, required: An open envelope for a plan, a context read or a committee result.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

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