Skip to main content
Invites are the mechanism for bringing new members into an organization. The admin-side endpoints create/list/revoke invites scoped to your org. The token-side endpoints let an invitee look up, accept, or decline an invite by its secret token — those endpoints don’t require you to be a member of the target org (the token itself identifies it).

Endpoints

Invite object (admin list/create)

The list / create endpoints use a trimmed view that omits the raw token. For the by-token lookup see the token lookup response.
The raw invite token is only shown via the email link the invitee receives, not in API responses. If you need to craft your own invite UX, capture the token from the user-submitted URL rather than the API.

List pending invites

Returns a JSON array of Invite objects in pending state, sorted by created_at descending.

Send an invite

Returns 201 Created with the Invite object. The invitee receives an email containing a link of the form https://app.thunderphone.com/invite/{token}.

Revoke an invite

Returns 204 No Content. Only invites with status pending can be revoked.

Look up by token

Public lookup used by the dashboard’s invite-landing page. This endpoint is unauthenticated — the token itself is the credential. Used to render the “You’ve been invited to join Acme Ops” UI.
Response:

Accept an invite

The caller must be authenticated; their user is added to the target org with the role specified on the invite.
Returns 200 OK:

Decline an invite

Returns 204 No Content.

Request access to an invite

For a signed-in user who received an invite link addressed to a different email (e.g. a forwarded invite): emails the original inviter asking them to grant access to the caller’s account instead. No membership is created — the inviter decides.
No request body. Returns 204 No Content when the request email was sent.

Members

Manage members and roles after they join.

Organizations

Manage the org resource itself.