TTAPI uses a consistent JSON response structure across endpoints so your application can handle success and failure cases in a predictable way.Documentation Index
Fetch the complete documentation index at: https://docs.ttapi.io/llms.txt
Use this file to discover all available pages before exploring further.
Unified response format
Success
Failure
HTTP status codes
| HTTP code | Meaning | Common cause |
|---|---|---|
200 | Request succeeded | Submission or fetch succeeded |
400 | Bad request | Invalid or missing parameters |
401 | Unauthorized | Missing or invalid TT-API-KEY |
402 | Insufficient balance | Not enough quota |
404 | Not found | Wrong endpoint or missing resource |
429 | Too many requests | Short-term request rate exceeded |
499 | Queue exhausted | Not enough queue capacity for that product |
500 | Server error | Internal service failure |
504 | Timeout | Long-running synchronous request timed out |
Business statuses
The
status field inside the JSON body describes the task state at the business level.| Status | Meaning |
|---|---|
PENDING_QUEUE | Waiting in queue |
ON_QUEUE | In progress |
SUCCESS | Completed successfully |
FAILED | Task failed |
Common examples
Successful submission
Successful fetch
Parameter error
Invalid key
Notes
- For
4xxresponses, check the request first before retrying - For
5xxresponses, retry once or twice, then contact support if the issue persists - Save the returned
jobIdfor polling, webhook correlation, and troubleshooting