Revoke an invite
The member becomes removed and its grants go; then the invitee's account is deleted when it never set a password; an account with a password, or one that is still a member of another tenant, is left as it is. Revoking an invite whose member is still removed retries that step.
Authorization
bearer In: header
Path Parameters
Invite id
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/v1/invites/497f6eca-6276-4993-bfeb-53cbbbba6f08"Can invites be emailed? GET
Asks the identity service whether SMTP is configured. Without it, invite by link (`delivery: "link"`). An identity service that can't be asked is not an error: the answer is `email_available: false` with the reason.
Send an invite again POST
A new code is mailed (the old one stops working; an account with a password and a verified email gets the notice again instead), or with `delivery: "link"` (only for an invitee with no password and an unverified email whom no other tenant holds; others get 409 `link_not_allowed`) the response carries the new link as `invite_url` (once, `Cache-Control: no-store`, never stored or logged); either way the link's token changes and the invite lives another 72 hours. An expired invite can be resent. At most 5 sends per person per hour, the first invite included (429 `rate_limited`). The body may be left out (then `email`).