Resend invitation
Resends a pending invitation using only its public ID. Send no request body or query parameters; no Content-Type header is required for the bodyless POST. Bodies (including an empty JSON object or the former version field) and query parameters are rejected with invalid_request. The backend loads the current revision from the API key’s company and supplies it internally to the existing resend service. Clients do not fetch or send version, and this endpoint adds no idempotency-key support.
Requires API access Manage, Team & access Manage, and permission to manage the target. Existing account, subscription, staging and usage checks apply. No additional Growth or RBAC feature gate. Only IDs matching ^invite_[A-Za-z0-9]+$ are accepted; numeric IDs, UUIDs and acceptance tokens are invalid_request. Missing, accepted and foreign-company invitations are unavailable (resource_missing). No global cross-company lookup occurs.
For the current saved revision, the existing service renews the acceptance link and expiration and requests delivery. Both expired and unexpired pending invites can be resent. Original identity, permissions, created and invited_by remain unchanged. Each call reads the current state and is a fresh resend request. A repeat after a timeout can renew again and request another email, even when an earlier delivery is pending. The newer acceptance link replaces the earlier link. Do not automatically retry an uncertain result as if it were duplicate-safe; retry only when another resend is acceptable.
Returns 200 with the saved invitation and changed. Normally changed=true; if the revision changes between lookup and the service’s locked check, existing stale-version behavior may return changed=false. Existing matching pending-delivery retry behavior is preserved. No forced retry loop is added. Neither 200 nor changed=true guarantees email arrival. Enqueue-registration failure rolls back renewal; delivery may also fail after commit. For invitation_resend_failed, use bounded backoff only when another resend is acceptable.
Response version remains an informational opaque saved revision for compatibility, not an input requirement or acceptance credential. Public IDs retain their nullable contract; no numeric fallback, request-time backfill, acceptance token or internal delivery token is exposed. Accept new response fields and handle unknown future enums without inferring additional access. An internal revision failure is invitation_resend_failed with no client version parameter to correct.
Authorizations
API key prefixed with finta_
Path Parameters
^invite_[A-Za-z0-9]+$Response
Saved invitation; changed is normally true for renewal/delivery work and may be false if the revision changes concurrently. Email arrival is not guaranteed.