Branded API domain
You can expose your service API under a branded host so clients call a URL like https://{developer-domain}.api.tollara.ai/... instead of the default gateway path. The developer domain is set per owner; each service can optionally add a service domain for a dedicated hostname.
How the URL is built
The branded base domain (e.g. api.tollara.ai) is set by the platform. The developer sets a developer domain in their profile (e.g. acme), which becomes the host label when you invoke via owner-only branding. A service may set its own service domain (e.g. widgets), which combines with the developer domain in one DNS label, separated by a hyphen.
The resulting host is: {developer-domain}.api.tollara.ai or, when the service has a service domain, {developer-domain}-{service-domain}.api.tollara.ai. The path is the same path template as your endpoint (e.g. /orders/{id}).
Nested two-label service hosts (e.g. developer.service.api.tollara.ai) are not supported — they fall outside the platform TLS wildcard certificate for *.api.tollara.ai.
Configuration
- Developer: Set your developer domain in your developer profile. Use lowercase letters and numbers only (no hyphens). This becomes the owner-only host label for all your services unless you add a per-service domain.
- Service: Optionally set a service domain on the service for a dedicated hostname (
developer-servicecomposite label). Service domains may include internal hyphens (e.g.data-pipeline).
Clients use the same Authorization: Bearer <service-key> header. The gateway resolves the subscription and forwards to your backend the same way as path-based invocation.
Example
Developer domain acme, service domain widgets, base domain api.tollara.ai → host acme-widgets.api.tollara.ai. A GET to https://acme-widgets.api.tollara.ai/orders/123 with a valid service key is forwarded to your endpoint that matches path /orders/{id}.
