tnl.dev :: api
api problems
Control, authority, ingress, and relay APIs return application/problem+json with a code, status, and request ID. Match the code and include the request ID when reporting a persistent failure.
request
- invalid_request — Request parameters or the body are invalid.
- traffic_selection_invalid — The requested traffic limits are invalid or exceed server policy.
- invalid_argument — An argument is invalid.
- invalid_json — The request body is not a single valid JSON value.
- unsupported_media_type — The request is not sent as application/json.
- member_hostname_depth_exceeded — The requested hostname has too many labels beneath its managed-domain namespace.
authentication
- unauthenticated — Authentication is missing or invalid.
- source_sign_in_required — current company source authentication or its required control-session backing is missing.
- verified_email_required — the issuer has not verified the signed-in identity's email for invitation acceptance.
authorization
- forbidden — The authenticated identity cannot perform this operation.
- manager_required — current service management permission is required for this operation.
- custom_domains_disabled — This server does not allow teams to add new custom domains.
- guest_demo_only — A guest credential can publish only the built-in demo with its secret visitor link.
- guest_ip_changed — The guest trial was issued from a different IP address.
- guest_trial_exhausted — The guest trial expired or used its ready time allowance.
resource
- not_found — The requested resource was not found or is not visible to this identity.
state
- conflict — The requested operation conflicts with current state.
- project_managed — An applied project revision manages this service.
- name_unavailable — The requested name is unavailable.
- publish_run_open — This public URL already has an open publish run.
- policy_revision_stale — Authorization policy changed since the request was prepared.
- stale_network_binding — The connector's network binding is no longer current.
- idempotency_conflict — An idempotency key was reused with different content.
- credential_delivery_unavailable — The resource was created, but its one-time credential cannot be delivered again.
- status_conflict — The reported state is no longer current.
provisioning
- dns_setup_pending — Required DNS setup is not yet ready.
- placement_unavailable — Distinct relay services are not available for this publish run.
- issuance_retry — Certificate issuance needs another attempt.
availability
- rate_limited — The API has limited the request rate.
- guest_issuance_limited — Guest demo creation is limited on this network.
- unavailable — The service is temporarily unavailable.
- temporarily_unavailable — The service is temporarily unavailable.
- internal — The service could not complete the operation.
internal coordination
- ingress_already_running — Another ingress process holds this identity's lease.
- ingress_lease_stale — The ingress process lease is no longer current.
- routing_table_resnapshot_required — The routing-table revision is no longer available.
- recovery_episode_stale — The recovery episode is no longer current.
- relay_registration_conflict — Relay registration conflicts with live state.
- relay_lease_stale — The relay lease is no longer current.
- certificate_unavailable — The relay transport certificate is not ready.
- stale_connection_assignment — The publisher connection assignment is no longer current.
- publisher_connection_already_claimed — Another relay process already claimed this publisher connection.
- invalid_publisher_connection_credential — The publisher connection credential is invalid.
- relay_identity_mismatch — The relay identity does not match the assignment.
- relay_draining — The relay is draining and will not accept new work.
- relay_connection_capacity_exhausted — The relay cannot accept another publisher connection.
- publisher_connection_unavailable — The assigned publisher connection is unavailable.