Skip to content

Overview

Internal-zone endpoints reachable only via the internal (VPN) ingress. Standalone spec — NOT referenced from api.yaml, so it is excluded from the public bundle. The load-balancer and resolve routes are unauthenticated (the internal ingress is the boundary); tenant and account administration additionally requires a bearer credential carrying the matching capability.

Tenant & account provisioning

Superuser (bootstrap credential) — configures tenants.

  1. POST /v1/internal/tenant — create a tenant.
  2. POST /v1/internal/tenant/{sid}/api-key — hand the tenant its key.

Tenant admin (tenant API key) — configures its own accounts and their access.

  1. POST /v1/internal/account — create an account.
  2. POST /v1/internal/account/{sid}/api-key or POST /v1/user — provision access.
  3. Manage that account’s resources with X-Account-Sid.

Information

  • OpenAPI version: 3.0.3