Desk

Send Committee Linkedin Invite

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.

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

Path parameters

account_idinteger required

The account's mashup company id (cb_account_plans.account_id).

contact_idinteger required

The committee member to invite.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

notestring nullable

Optional invite note. Capped by LinkedIn at 300 characters.

Response

Successful Response

dataAccountPlanPayload required

An open envelope for a plan, a context read or a committee result.

Changes

No recorded changes to this operation across all 2 revisions of this API.