Skip to main content
DELETE
cURL
Legacy endpoint. /api/v1/invitations/{token}/ predates workspaces. It keeps working for existing integrations. New integrations should use Revoke an Invitation, its replacement under /api/v1/organization/invitations/.
Behaves exactly like Revoke an Invitation: the token path segment takes the invitation’s id, and revoking takes back every workspace, group, and grant the invitation carried.

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