team

Preview Invite

Public: what this invitation is, and whether it can still be used.

Rate limited per IP because it is the only unauthenticated endpoint here that reads a secret from the URL. The tokens are 32 random bytes, so guessing one is not a realistic attack — but an endpoint that answers unlimited guesses is worth throttling on principle rather than on arithmetic, and the same limit stops it being used to hammer the database.

get/api/team/invites/{token}/preview

Request

  • Base URL: https://api.heymetra.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.heymetra.com/api/team/invites/{token}/preview
  • Auth: none declared

Path parameters

tokenstring required

Response

Successful Response

state'valid' | 'expired' | 'revoked' | 'accepted' | 'unknown' required
tenant_namestring nullable
role'owner' | 'member'

Who somebody is in one workspace.

Two, by the owner's decision of 2026-09-18, and the argument is the one he made: four roles that collapse to two predicates are not four roles. OWNER and ADMIN differed in two lines in the whole codebase; EDITOR and VIEWER in one.

Worse, four roles plus per-connection grants meant the same fact could be stated twice and disagree — a role saying VIEWER while a grant said writer, with the winner decided across sixteen separate gates. One axis cannot express the contradiction.

OWNER does everything: billing, team, connecting accounts, approving changes, and reading and writing on every connection.

MEMBER does exactly what it was given, per connection, in connection_grants.level. A member with no row anywhere can sign in and see that nothing has been shared with them yet, and that is all.

Persisted as a plain string: VARCHAR(32), no CHECK constraint, no native Postgres type, so this is a code change and not a migration.

emailstring nullable
has_accountboolean nullable

Changes

No recorded changes to this operation across all 3 revisions of this API.