Update invitation
Updates only the permissions of a pending invitation in the API key’s company. Requires API access Manage, Team & access Manage, RBAC enabled, and an active or trialing Growth subscription for every edit, including Admin and unchanged requests. The person must be allowed both to manage the invitation’s existing access and to grant the requested access. Accepted invitations and unavailable or foreign-company invitations return resource_missing without exposing their data.
Only access_template and custom permissions are accepted in the JSON body. Names, email, version, and other fields are rejected; query parameters do not supply body fields. Presets admin/read_only reject permissions even null. Custom requires every catalog area with none/view/manage; api_access supports only none/manage. Extra areas are rejected. Responses label custom permissions matching a preset as that preset.
Only public IDs matching ^invite_[A-Za-z0-9]+$ are accepted. Numeric IDs, UUIDs, and acceptance tokens are invalid_request. No public-ID fallback or backfill occurs. Response IDs retain their nullable contract; never substitute a private identifier. Returns the saved invitation and changed=true when permissions differ, false otherwise. Does not send email, renew expiration, or change identity or original attribution. Expired pending invitations can be edited. Version remains an opaque saved revision; do not interpret it as a token or manufacture it. Allow new response fields and treat unknown enum values as unsupported, never as additional access. An uncertain result can be retried with the same body; authorization and plan checks still apply. Access is replaced as a complete permission set, not merged as a partial update. There is no version precondition or compare-and-swap: a later authorized edit can overwrite earlier permissions. Fetch current state when needed. Resend, revoke, and accepted-member management are separate operations.
Authorizations
API key prefixed with finta_
Path Parameters
^invite_[A-Za-z0-9]+$Body
- Option 1
- Option 2
The template matching stored permissions. Admin means all areas have manage access. Read_only means view access for every area except api_access, which is none. Custom means neither template matches exactly; inspect permissions for the actual access.
admin, read_only Stored company permissions shown on the Settings team page. All areas are always included. None means no access to the area; view means read access; manage means management access. API access supports none or manage; other areas also support view.
Response
Saved invitation; changed indicates whether permissions differed.