InvitationIssuedOut

Response for the two endpoints that MINT a token: create and resend.

Carries invite_link -- byte for byte the same link the invitation email contains -- so the caller who just created the invitation can render it as a QR code for on-site check-in without a second token transport. The token is stored hashed and is unrecoverable afterwards, which is why the listing schema deliberately still omits it: InvitationOut never exposes a token, and only the authenticated owner/manager making this very request sees it.

idId (string)required

emailEmail (string)required

roleRole (string)required

statusStatus (string)required

created_atstring<date-time>required

expires_atstring<date-time>required

invited_by_email object

anyOf

• string
• null

string

invite_linkInvite Link (string)required

invite_ttl_hoursInvite Ttl Hours (integer)required

InvitationIssuedOut

{
  "id": "string",
  "email": "string",
  "role": "string",
  "status": "string",
  "created_at": "2024-07-29T15:51:28.071Z",
  "expires_at": "2024-07-29T15:51:28.071Z",
  "invited_by_email": "string",
  "invite_link": "string",
  "invite_ttl_hours": 0
}