> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veilroute.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> HTTP status codes returned by the sensor API.

Every error returns a JSON body with a single `error` field. Messages are intentionally generic and
never reveal why a request failed — rely on the **status code**, not the message.

```json theme={null}
{ "error": "request failed" }
```

| Status | Meaning | What to do |
| - | - | - |
| `200` | Sensor generated. | Use it. |
| `400` | The request body was missing or invalid. | Check your JSON and required fields (`app` is required on BMP). |
| `401` | Missing or invalid API key. | Verify the `X-Api-Key` header and that the key matches this product. |
| `429` | Rate limit exceeded for your key. | Back off and retry — see [Rate limits](/rate-limits). |
| `503` | The service could not generate a sensor right now. | Retry with backoff; if it persists, contact support. |
| `404` | Unknown path. | Check the method and URL (`POST /api/v1/sensor`). |

> [!TIP]
>
> Log the status code and your own request id so you can trace a failure without relying on the
> response message.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.