Organizations

Every Tauth user belongs to exactly one organisation. The organisation is the billing and access boundary.

Creating an organisation

An organisation is created automatically when the first user registers with a given org_name:

POST /auth/register
{ "email": "...", "password": "...", "org_name": "Acme Media" }

The org slug is derived from the name (e.g. acme-media).

Inviting team members

Only admin users can invite new members.

POST /org/invite
Authorization: Bearer eyJ...
Content-Type: application/json

{
  "email": "bob@example.com",
  "password": "temporary-password",
  "role": "signer"
}

The invited user can log in immediately with the supplied credentials.

Listing users

GET /org/users
Authorization: Bearer eyJ...

[
  { "user_id": "uuid", "email": "alice@example.com", "role": "admin" },
  { "user_id": "uuid", "email": "bob@example.com",   "role": "signer" }
]

Managing API keys

See Authentication → API keys for the full flow.

To list all keys for your org:

GET /org/api-keys
Authorization: Bearer eyJ...

[
  { "key_id": "uuid", "name": "ci-pipeline", "created_at": "2025-01-15T10:00:00Z" }
]

Note: the raw key value is never returned by the list endpoint.