> For the complete documentation index, see [llms.txt](https://docs.blinklabs.xyz/blink/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blinklabs.xyz/blink/data-api/orders-api.md).

# Orders API

Per-order landing, refund and auction data for the transactions you send to Blink

{% hint style="warning" %}
The Orders API is off by default. To enable it for your account, reach out to us at <contact@blinklabs.xyz>.
{% endhint %}

The Orders API reports on the transactions (orders) you send to Blink: when each was received, whether and where it landed, its MEV refunds and backruns, and aggregate inclusion statistics. It is compatible with the [NovaRPC Data API](https://docs.novarpc.xyz/data-api), so an existing Nova integration only needs a new base URL and API key.

## Endpoint & Authentication

```
https://api.blinklabs.xyz/v1/{chain}/
```

Replace `{chain}` with one of:

* `eth` (Ethereum mainnet)
* `base` (Base)
* `bsc` (BNB Smart Chain)
* `arbitrum` (Arbitrum One)
* `robinhood` (Robinhood Chain)
* `arc` (Arc)

Ethereum mainnet is enabled separately from the other chains; mention it when you request access.

### Authentication

Authenticate with your Blink API key, the same key as in your Blink RPC URL. Include it in the `Authorization` header of each request:

```
Authorization: Bearer <your-api-key>
```

The key can also be passed as an `api_key` query parameter or an `X-Api-Key` header.

### Endpoints

| Endpoint                                                                         | Description                                            |
| -------------------------------------------------------------------------------- | ------------------------------------------------------ |
| [`POST /order`](https://docs.blinklabs.xyz/blink/data-api/orders-api/order.md)   | Details for a single order                             |
| [`POST /orders`](https://docs.blinklabs.xyz/blink/data-api/orders-api/orders.md) | Statistics and details for all orders in a time window |

### Requests and responses

* Request bodies are JSON and must be sent with `Content-Type: application/json`.
* Optional HTTP compression is supported both ways. Compress the request body and set `Content-Encoding`, or ask for a compressed response with `Accept-Encoding`. Supported encodings: `zstd`, `gzip`, `br` (Brotli).
* Amounts are strings holding integers in wei (e.g. `"41580000000000"`), so they never lose precision.
* Timestamps are RFC 3339 in UTC (e.g. `2026-11-06T09:00:22.727482Z`).

### Rate limits

Each API key can make 100 requests per minute. Requests over the limit return `429`.

### Errors

API errors return a JSON body with an `error` message:

```json
{"error": "Invalid API key"}
```

| Status       | Meaning                                                                        |
| ------------ | ------------------------------------------------------------------------------ |
| `400`        | Unsupported chain, or an invalid request (e.g. `end_time` before `start_time`) |
| `401`        | Missing or invalid API key                                                     |
| `413`        | Request body over 1 MiB                                                        |
| `415`        | Missing `Content-Type: application/json`                                       |
| `422`        | A required field is missing or has the wrong type (plain-text body)            |
| `429`        | Rate limit exceeded                                                            |
| `500`, `502` | Temporary error; retry the request                                             |
