> ## Documentation Index
> Fetch the complete documentation index at: https://85b42a7-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://85b42a7-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://85b42a7-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://85b42a7-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Check orders are available (/docs/api/store-data/orders-get-availability)

<!-- agent-signals: reading_time_min: 1 · est_tokens: 599 · updated: 2026-11-16 -->
Related: [Get analytics status](/docs/api/store-data/analytics-get-status.md), [Query the lake](/docs/api/store-data/data-query.md), [Get an insight card](/docs/api/store-data/insights-get.md), [Get inventory state](/docs/api/store-data/inventory-get-state.md), [Get an order](/docs/api/store-data/orders-get.md), [List orders](/docs/api/store-data/orders-list.md)

> Whether this Product Metrics environment serves store orders at all.

`GET https://prod-backend.productmetrics.io/api/public/v1/orders/availability`

**Scope** `read` · **Access** Read only · **Operation id** `orders.get_availability`

## Try it

`productmetrics` runs after `productmetrics login`; curl needs `PM_TOKEN` (see [Authentication](/docs/api/overview#authentication)).



**productmetrics CLI:**

```bash
productmetrics orders get-availability --json
```

**curl:**

```bash
curl "https://prod-backend.productmetrics.io/api/public/v1/orders/availability" \
  -H "Authorization: Bearer $PM_TOKEN"
```

## Response

API response (200):

```json
{
  "data": {
    "available": true
  },
  "request_id": "req_01JP1NMYWCCABXND7M1EJ98H24"
}
```

**CLI output:** `productmetrics orders get-availability --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

Call once before [`orders.list`](/docs/api/store-data/orders-list) when it is unclear; when `available` is false, the order operations answer not found.

## Errors

A failure answers with its HTTP status and `{ error: { code, message, details? }, request_id }`. Branch on `code` (stable, lower_snake); show `message` to the person. The CLI prints the same `error` with `"ok": false`.

```json
{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the read scope; connect again and allow it.",
    "details": {
      "required_scope": "read"
    }
  },
  "request_id": "req_01JZXWG3TJPWZ6C69CH3C7C0YZ"
}
```

| Status | Code                 | When                                                                                                                      |
| ------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| 401    | `invalid_token`      | The token is missing, expired or revoked: sign in again (`productmetrics login`). The `WWW-Authenticate` header says why. |
| 403    | `insufficient_scope` | The token lacks the `read` scope (`details.required_scope`): sign in again and allow it.                                  |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Store data and insights operations](/docs/api/store-data)
