tnl.dev :: api
api problems
Problem type URLs in application/problem+json. Public API clients should use the structured code and status; internal coordination problems identify private tnld service failures.
request
- invalid_request — Request parameters or the body are invalid.
- invalid_argument — An argument or usage report 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.
authentication
- unauthenticated — Authentication is missing or invalid.
authorization
- forbidden — The authenticated identity cannot perform this operation.
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.
- 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.
- idempotency_conflict — An idempotency key was reused with different content.
- 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.
- 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.
- invalid_usage_report — An ingress usage report is invalid.
- usage_route_not_found — The reported publish run was not found.
- stale_usage_report — A newer usage report revision is already recorded.
- usage_report_conflict — The usage report conflicts with stored data.
- usage_bucket_finalized — The usage bucket is already finalized.
- 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.