Errors
Errors answer a JSON body with a code (the tRPC error code, e.g. UNAUTHORIZED, FORBIDDEN, NOT_FOUND, CONFLICT) and a message:
{ "code": "NOT_FOUND", "message": "..." }| Status | Meaning |
|---|---|
400 |
The JSON body is malformed or fails the input validation. |
401 |
The API key is missing, invalid, disabled or expired. |
403 |
The API key lacks the scope, or its owner lacks the dashboard permission. |
404 |
The resource does not exist in the organization of the API key. |
409 |
The request conflicts with the resource state. |
412 |
A precondition failed, e.g. the organization balance does not cover the launch. |
429 |
The API key exceeded its rate limit; retry after the Retry-After seconds. |
500 |
Unexpected server error. |
Validation errors
Section titled “Validation errors”A body that fails the input validation answers 400 with the Zod issues. Each path locates the invalid field in the procedure input:
{ "message": "Validation Error", "errors": [ { "code": "invalid_type", "message": "...", "path": ["budget"] } ]}A malformed JSON body answers 400 with:
{ "message": "Invalid JSON body" }© 2026 Wortise. All rights reserved.