Errors

All errors return a JSON body with a detail field describing what went wrong.

{ "detail": "Invalid client credentials" }

---

HTTP error codes

Status	When it occurs
401 Unauthorized	The client_id or client_secret is incorrect
422 Unprocessable Entity	A required field is missing, or a field has an invalid value (e.g. wrong grant_type, malformed date)
500 Internal Server Error	Something went wrong on our side
503 Service Unavailable	The portal backend could not be reached — safe to retry

---

401 — Invalid credentials

Returned when the client_id or client_secret in the auth request is wrong.

{ "detail": "Invalid client credentials" }

Check that you are using the exact credentials provided by Track32. If you believe your credentials are correct, contact support.

---

422 — Validation error

Returned when the request is missing required fields or contains an invalid value.

{
  "detail": [
    {
      "type": "missing",
      "loc": ["body", "grant_type"],
      "msg": "Field required"
    }
  ]
}

Common causes:

• grant_type is missing or not set to client_credentials
• start_date or end_date is not a valid UTC ISO 8601 datetime
• start_date or end_date has no timezone (must end with Z or +00:00)

---

500 — Internal server error

An unexpected error on our side. If it persists, contact support with the request details and timestamp.

---

503 — Service unavailable

The portal backend was unreachable. This is transient — wait a few seconds and retry. If it persists, contact support.

Retrying safely

GET /v1/batches and GET /v2/batches are read-only and safe to retry. For 503 responses, retry with a short delay (e.g. 3–5 seconds).