TEteaflask
authed

Revoke Invitation

Kill the link. Idempotent on revoked/expired rows; an accepted invitation refuses — the membership it minted is the thing to remove. 404 for unknown AND foreign ids alike: another org's row is invisible under the tenant policy, so existence stays unprobeable.

post/api/v1/organizations/current/invitations/{invitation_id}/revoke

Request

  • Base URL
    https://api.teaflask.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.teaflask.com/api/v1/organizations/current/invitations/{invitation_id}/revoke
  • Auth
    none declared

Path parameters

invitation_idstring uuid required

Response

Successful Response

idstring uuid required
emailstring required
role'owner' | 'member' required
status'pending' | 'accepted' | 'revoked' | 'expired' required

The invitation lifecycle (the CHECK's mirror). pending is the only live state; accepted, revoked, and expired are terminal. expired may also be stamped lazily after expires_at passes — readers judge a pending row by its deadline, not this label alone.

expires_atstring date-time required
created_atstring date-time required

Changes

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