Skip to main content
DELETE
cURL
Revoking is not just cancelling an email. Because an invitation provisions the person the moment it is sent, they may already be carrying groups and grants — so revoking takes all of it back.
Revoking removes every grant on all three permission axes, and every group membership. If the invitation was the only reason that person existed in Nekt, the account is deleted too. This cannot be undone: re-inviting them starts from nothing.

The path parameter is the id

The URL segment is named token, but the value is the invitation’s id — the field you get from List Invitations. Passing the invitation token instead returns 404.

Response

200, with a confirmation body.

Revoke versus letting it lapse

These are different, and the difference is the access: An expired invitation is a pause — resend it and the person picks up exactly where you left them. A revoked one is a decision. Revoke when somebody is not joining; let one lapse when they are simply slow.

Clean up invitations nobody answered

Errors

Authorizations

x-api-key
string
header
required

API Key authentication. Format: 'x-api-key: api_key'

Path Parameters

token
string<uuid>
required

The invitation's id. Despite the name, this is not the invitation token.

Response

200 - application/json
detail
string
required