---
title: "Send a connect-request"
method: POST
path: "/v1/{account_id}/invites"
tags: ["Invites"]
---

# Send a connect-request

`POST /v1/{account_id}/invites`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/invites`
- Auth: HTTP bearer

Sends a connect-request to a member by public identifier or URN. Supports an optional note. The note is passed to the platform and immediately discarded, never stored.

## Path parameters

- `account_id` string, required

## Request body

- object
  - `recipient_identifier` string, required: LinkedIn public identifier (vanity slug) or member URN of the recipient.
  - `message` string: Optional connect-request note (up to 300 characters). Passed to the platform and immediately discarded, never stored.

## Response `201`

Connect-request sent successfully.

- object
  - `object` 'invitation_sent', required: Response type discriminator.
  - `id` string, required: Direction-prefixed connect-request id (SENT_...).
  - `status` 'sent', required: Outcome status.
  - `created_at` string: ISO-8601 UTC timestamp when the connect-request was created. Optional, omitted when the platform does not return it.
  - `message` string: Echoed note, when the platform returns it.
  - `user` object: The recipient's member object (sent-variant, sparser than received).
    - `id` string, required: Native LinkedIn member URN.
    - `type` 'individual' | 'organization' | 'other': Member type.
    - `display_name` string: Display name.
    - `first_name` string: First name.
    - `last_name` string: Last name.
    - `public_picture_url` string: Public profile picture URL.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `400`: Invalid request, missing or malformed parameters.
- `401`: Missing or invalid API key.
- `404`: Account not found or not owned by this tenant. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `409`: A connect-request to this member already exists, or you are already connected (CONNECTION_REQUEST_CONFLICT). Do not re-send.
- `413`: Payload too large, the request body exceeds the size limit.
- `422`: Account restricted from performing this operation.
- `429`: Quota exceeded, slow down and retry after the hinted delay.
- `500`: Internal server error.
- `502`: The platform did not complete the invitation, or is temporarily unavailable. When `retry_hint` is `never`, the invitation may already have been delivered and re-sending would send a second one: read the sent invitations before trying again. The per-response `retry_hint` and `retry_likely_to_succeed` are authoritative, not the general meaning of the code.
- `503`: Service unavailable.
- `504`: Gateway timeout.

---

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