Invites

Resend a pending invite

Mints a fresh token and a fresh 7-day expiry for a pending invite, swapped onto the same row — the invite id is unchanged and the previous link stops working. The answer to "the invite email never arrived": creating the same invite again is refused as a duplicate (409), so this is the route that sends a new link. The raw token comes back once, as on create. The caller's own grant ceiling is re-checked against the invite's role, so resending can never hand out a role the caller could not grant. Requires member:manage. A browser session must also pass a fresh step-up reauthentication in the app (without it the call answers 428 step_up_required). An organization API token is not challenged.

post/invite/{id}/resend

Request

  • Base URL: https://api.elaichi.ai
  • URL: https://api.elaichi.ai/invite/{id}/resend
  • Auth: HTTP bearer

Path parameters

idstring required

Invite id (inv_…).

Headers

X-Organization-Idstring

Target organization (org_…). Required for cookie/session auth on org-scoped routes; optional for API tokens, which carry their organization, and rejected when it names a different one.

Response

Resent

idstring

Invite id (inv_…).

emailstring email

Lowercased at creation.

role_idsstring[]

The single role (role_…) the invitee receives on acceptance.

team_idsstring[]

Teams (team_…) they are added to.

statusstring

Lifecycle state; only pending invites can still be accepted.

expires_atstring date-time

Seven days after creation.

invited_bystring nullable

User id (usr_…) of the inviter.

created_atstring date-time
updated_atstring date-time
tokenstring

Raw invite token — returned once, never retrievable again.

email_sentboolean

False when no invite email went out (the token still works).

Changes

No recorded changes to this operation across all 1 revision of this API.