tracera
API

Management API

Programmatic control of the entities that currently ship: account, signup, brands, properties, memberships. Useful for IaC and multi-tenant resellers.

Base URL & auth

https://portal.tracera.eu/api/v1/
Authorization: Bearer tk_live_EXAMPLE

Token scope determines what you can touch. A tenant_admin token can manage anything inside its tenant; a brand_manager token can manage one brand's properties.

Account

GET    /v1/me                       # current user
POST   /v1/me/password               # change password
POST   /v1/signup                    # create a new account + tenant

Brands & properties

GET    /v1/properties                          # list properties visible to the token
GET    /v1/tenants/<tid>/brands
POST   /v1/tenants/<tid>/brands
POST   /v1/brands/<bid>/properties

Property create example

POST /v1/brands/brd_a1b2/properties
{
  "name": "example.com web",
  "type": "web",
  "timezone": "Europe/Brussels",
  "domains": ["example.com", "www.example.com"]
}

# Response:
{
  "id": "prp_3f09c2e",
  "public_key": "pk_a3f09c2e71bd",
  "name": "example.com web",
  "type": "web",
  "domains": [{ "id": "dom_1", "value": "example.com" }],
  "created_at": "2026-06-17T08:42:11Z"
}

Memberships

DELETE /v1/memberships/<mid>            # remove a member
Token secrets are only shown on creation; subsequent reads return just the metadata (we keep an Argon2 hash, not the plaintext).