# Errors

What each status code means, and what to do about it.

## Status codes

| Code | Meaning | What to do |
| --- | --- | --- |
| `200` | OK | The response body holds the requested resource. |
| `400` | Bad Request | The request is invalid (missing parameter, wrong body shape). Fix the call and resend. Don't retry. |
| `401` | Unauthorized | The token is wrong, revoked, or missing. Check the `Authorization: Bearer itr_pat_...` header. Don't retry until the token is fixed. |
| `403` | Forbidden | The token is valid but lacks the required scope. Add the right `Api: ...` scope on the token's Privileges page in IntelliTracer. Don't retry. |
| `404` | Not Found | The resource doesn't exist, or not within your tenant. Check the `Id` and the path. Don't retry. |
| `429` | Too Many Requests | You hit the rate limit. Wait the number of seconds in the `Retry-After` header and try again. See [Rate limits](/docs/rate-limits). |
| `500` – `504` | Server-side error | Transient. Retry with exponential backoff (see below). If the failure persists past 5 attempts, escalate to [support](https://geodynamics.eu/nl-be/support/). |

## More

-   [Rate limits](/docs/rate-limits) for the exact budgets and throttle window.
-   [Authentication](/docs/authentication) for resolving `401` and `403`.