Error Codes

View Markdown

Error format

All API errors return a JSON object with kind and message fields:

{
  "kind": "task_not_found",
  "message": "The task does not exist. Verify the task ID."
}
FieldTypeDescription
kindstringA specific error identifier in snake_case
messagestringActionable guidance for the user

Common error kinds

KindStatusDescription
token_missing401No auth token provided
token_invalid401Auth token is invalid or revoked
project_required403Endpoint requires a project-scoped key
request_invalid400Request body failed validation
url_required400Source URL is required
format_unsupported400Format not supported for this task kind
task_not_found404Task does not exist
run_not_found404Run does not exist
automation_not_found404Automation does not exist
payment_required402A payment is required to continue using this service
internal_error500Server-side error

4xx Client Errors

400 Bad Request

The request was invalid. This is usually caused by a missing required parameter or invalid value. The kind and message fields will help identify the specific issue.

401 Unauthorized

Authentication is required. Include an API key in the Authorization header:

Authorization: Bearer ITTYBIT_API_KEY

402 Payment Required

A payment issue exists on the account. Visit billing to resolve.

403 Forbidden

The API key is valid but does not have access to the requested resource or action.

404 Not Found

The requested resource was not found. Verify the resource ID.

405 Method Not Allowed

The HTTP method is not supported for this endpoint.

408 Request Timeout

The request took too long to complete.

429 Too Many Requests

Rate limit exceeded. Reduce the frequency of requests.


5xx Server Errors

500 Internal Server Error

An unexpected error occurred on our side. If you encounter this error, please contact support and we will look into it immediately.

502 Bad Gateway

An invalid response was received from a downstream server.

503 Service Unavailable

The server is temporarily unable to handle requests. Please try again later.

On this page