---
title: "Invite connections to follow a company page"
method: POST
path: "/v1/{account_id}/companies/{identifier}/follow-invite"
tags: ["Companies: Profile"]
---

# Invite connections to follow a company page

`POST /v1/{account_id}/companies/{identifier}/follow-invite`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/companies/{identifier}/follow-invite`
- Auth: HTTP bearer

Invites one or more of the connected account's 1st-degree connections to follow a company page it administers, using member ids from an invitable-followers read. All-or-nothing: one invalid invitee id rejects the whole request (404). Re-inviting an already-invited member is a safe no-op.

## Path parameters

- `account_id` string, required
- `identifier` string, required

## Request body

- object
  - `invitee_ids` string[], required: The AC... member ids to invite to follow the page. Each is the id field of an invitable-followers read. Required, 1 to 50 per request.

## Response `200`

One per-invitee outcome for each requested member, in request order, for an all-valid request. If any invitee id is invalid, the whole request is rejected (404), with no partial success. Re-inviting an already-invited member returns the same invitation id with status "already_invited"; calling again never creates a duplicate. Only identifiers transit; nothing is stored.

- object
  - `object` 'company_follow_invite_result', required: Response type discriminator.
  - `results` object[], required: One entry per requested invitee, in request order, for an all-valid request. If any invitee id is invalid, the whole request is rejected (404), with no partial success.
    - `object` 'company_follow_invite', required: Item type discriminator.
    - `invitee_id` string, required: The member id from the request, echoed back.
    - `status` 'invited' | 'already_invited' | 'ineligible' | 'not_found', required: Per-invitee outcome. "invited": a new follow-invitation was created. "already_invited": a pending invitation already existed; calling again returns the same invitation_id, never a duplicate. "ineligible": the member is not an invitable 1st-degree connection. "not_found": the member id did not resolve.
    - `invitation_id` string, nullable, required: The invitation id, present for "invited" and "already_invited", null for a per-invitee failure.
    - `error` object, nullable, required: Present only for a per-invitee failure ("ineligible" / "not_found"); null otherwise.
      - `code` string: Canonical error code for this invitee's failure.
      - `message` string: Human-readable failure reason.
  - `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`: Empty, over-cap (>50), or malformed invitee_ids, or a non-numeric identifier, rejected before any send.
- `401`: Missing or invalid API key.
- `403`: The account does not administer this page with the invite-to-follow entitlement (fail-closed), or lacks an active seat.
- `404`: The account_id does not belong to this tenant, or a wholly-invalid invitee did not resolve. 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.
- `413`: Payload too large, the request body exceeds the size limit.
- `422`: The account is restricted and cannot perform this operation.
- `429`: The follow-invite credit or rate budget is exhausted. Slow down and retry after the hinted delay.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `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)