# List orders for a store

> Eto API reference for `GET /api/v1/orders/{shop_id}`. Base URL `https://eto.tools/api/v1/`. Authenticate with the `X-Eto-API-Key` header.

Part of the [Eto API reference](https://eto.tools/dev/docs/). The full reference in one file is at [llms-full.txt](https://eto.tools/dev/docs/llms-full.txt); the machine-readable schema is at [openapi.json](https://eto.tools/dev/docs/openapi.json).

## GET /api/v1/orders/{shop_id}

List orders for a store

- Operation ID: `orders_list`
- Slug: `orders-list`
- Category: Orders
- Authentication: API key only. Reads or writes data Eto holds for your own account.
- HTML: https://eto.tools/dev/docs/#ep-orders-list
- Markdown: https://eto.tools/dev/docs/orders/orders-list.md

List receipts/orders for a connected store (newest first by default — so for "my latest order" just call this, no date filter). Triggers a background sync so data stays fresh. To filter by date, pass a friendly `period` or `start_date`/`end_date` (resolved server-side in the shop timezone) — do NOT compute unix timestamps. Every order includes `created_iso` (UTC) and `created_local` (shop/your timezone), and the response carries `server_now_utc` + `timezone`, so you never mis-read a raw timestamp or think an order is "in the future".

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Connected shop id |
| `limit` | query | `integer` | no | Page size (default 25) |
| `offset` | query | `integer` | no | Pagination offset |
| `period` | query | `string` | no | Friendly date filter: today, yesterday, last_7_days, last_30_days, this_month, last_month. |
| `start_date` | query | `string` | no | Filter from this calendar day "YYYY-MM-DD" (inclusive). |
| `end_date` | query | `string` | no | Filter to this calendar day "YYYY-MM-DD" (inclusive). |
| `timezone` | query | `string` | no | IANA tz for resolving period/dates + formatting created_local (default: shop tz). |
| `min_created` | query | `integer` | no | Advanced: unix lower bound on order creation. Prefer period/start_date. |
| `max_created` | query | `integer` | no | Advanced: unix upper bound on order creation. Prefer period/end_date. |
| `sort_on` | query | `string` | no | Sort field (default "created") |
| `sort_order` | query | `string` | no | asc or desc (default desc) |

### Request

```bash
curl -X GET "https://eto.tools/api/v1/orders/12345678?limit=25&offset=0" \
  -H "X-Eto-API-Key: eto_your_key"
```

```python
import requests

url = "https://eto.tools/api/v1/orders/12345678"
headers = {"X-Eto-API-Key": "eto_your_key"}
params = {
    "limit": 25,
    "offset": 0
}

response = requests.get(url, headers=headers, params=params, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/orders/12345678?limit=25&offset=0";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`. This endpoint has no worked response example in the registry yet; the [HTML reference](https://eto.tools/dev/docs/#ep-orders-list) shows the fields it returns.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.