Skip to main content

Documentation Index

Fetch the complete documentation index at: https://api-docs.tiro.ooo/llms.txt

Use this file to discover all available pages before exploring further.

​
Error Response Format

All Tiro API errors follow a consistent JSON structure: 
{
  "error": {
    "code": 400001,
    "errorType": "bad_request",
    "message": "Human readable error message",
    "detail": "Additional context or null"
  }
}

​
Fields

FieldTypeDescription
codeinteger6-digit error code in AAABBB form: first 3 digits match the HTTP status, last 3 digits are a per-status serial. Use this for fine-grained client branching.
errorTypestringCoarse-grained category derived from the HTTP status. Stable over time — safe for client branching. See table below.
messagestringHuman-readable error message. Not stable; do not use for branching.
detailobject | string | nullOptional additional context (varies per error).

​
HTTP Status Codes & Error Types

StatuserrorTypeMeaning
400bad_requestInvalid request format or parameters
401unauthorizedMissing or invalid API key
403forbiddenAPI key lacks required permissions
404not_foundResource doesn’t exist
406not_acceptableUnsupported Accept header
409conflictResource already exists or state conflict
413payload_too_largeRequest body exceeds size limits
422unprocessable_entityValid format but invalid data
429too_many_requestsRate limit exceeded
5xxinternal_errorServer-side error (do not parse further; retry with backoff)