Getting started
Errors
Error responses are JSON with a message, and per-field errors for validation failures. What each status code means.
Error format
Errors are JSON with a message, plus errors per field for a 422.
422 Unprocessable ContentJSON
{
"message": "The subject field is required.",
"errors": {
"subject": [
"The subject field is required."
]
}
}Status codes
| Status | Meaning |
|---|---|
| 401 | Missing, invalid or expired token, an OAuth app the user disconnected, or a browser session instead of a token. |
| 403 | Token not scoped to a team you belong to, team not on Premium, IP not allowed, the token lacks the scope the endpoint needs (the message names it), or no permission for that ticket or resource (e.g. customers need an admin or owner token). |
| 404 | Not found, or not visible to the token (other teams' records always answer 404). |
| 409 | The ticket was merged into another one; merged_into names it. |
| 422 | Validation failed; errors lists the problems per field. |
| 429 | Rate limit (or the team's monthly ticket limit) reached. |