TEteaflask
authed

Create Invitation

Mint an invitation and email its accept link. The response is the only time the full link is ever shown — the row keeps the token's hash. The email is best-effort: the row is durable and the link was revealed, so a failed send costs a log line, never the 201.

post/api/v1/organizations/current/invitations

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
  • Auth
    none declared

Request body

emailstring required
role'owner' | 'member' 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
invite_linkstring required

Changes

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