# GET /v1/shops/{id}/exceptions

> The shop's exceptions: the reorder points people fixed by hand, and the products they keep off the stop-stocking list.

Markdown twin of https://panlytics.net/developers/api/exceptions-list (last updated 2026-10-25). Every page of the Panlytics developer docs is listed at https://panlytics.net/developers/llms.txt, and all of them are in one file at https://panlytics.net/developers/llms-full.txt. The site guide is https://panlytics.net/llms.txt.

## What it does

As the Exceptions page lists them, newest first. A person limited to chosen categories sees the rules for their own products only.

## Who may call it

A key whose maker's role holds `figures` (see the figures), after the fence, for the shop or category it names.

## Request

```http
GET https://panlytics.net/api/v1/shops/{id}/exceptions
```

### Parameters

| Name | In | Type | Required | What it is |
| --- | --- | --- | --- | --- |
| `id` | path | integer | Yes | The shop's id. |
| `cursor` | query | string | No | The `nextCursor` of the page before. Leave it out for the first page. Treat it as an opaque string. |
| `limit` | query | integer | No | How many rows on one page: 1 to 200, 50 when left out. |
| `Authorization` | header | string | Yes | Bearer, a space, then the key. |

### Example request

```bash title="curl"
curl https://panlytics.net/api/v1/shops/12/exceptions \
  -H "Authorization: Bearer $PANLYTICS_KEY"
```
```python title="Python"
import os

import requests

response = requests.get(
    "https://panlytics.net/api/v1/shops/12/exceptions",
    headers={"Authorization": f"Bearer {os.environ['PANLYTICS_KEY']}"},
    timeout=60,
)
response.raise_for_status()
print(response.json())
```
```typescript title="TypeScript"
const response = await fetch("https://panlytics.net/api/v1/shops/12/exceptions", {
  headers: {
    Authorization: `Bearer ${process.env.PANLYTICS_KEY}`,
  },
});
if (!response.ok) throw new Error(`Panlytics answered ${response.status}`);
console.log(await response.json());
```

## Response

`200`: The answer, as JSON.

| Field | Type | Always there | What it is |
| --- | --- | --- | --- |
| `data[]` | object[] | Yes | The rows of this page. |
| `data[].productId` | string | Yes | The product's id, usually its barcode (EAN). |
| `data[].name` | string or null | Yes | What the product is called, or null when no report of the shop holds it. |
| `data[].category` | string or null | Yes | The category the product was found in, or null. |
| `data[].keepAt` | integer or null | Yes | The reorder point a person fixed for it, or null when the rule fixes no level. |
| `data[].neverStop` | boolean | Yes | True when the product must never be put on the stop-stocking list. |
| `data[].reason` | string | Yes | Why, in the words of the person who set it. |
| `data[].setBy` | string or null | Yes | Who set it, or null once their account is gone. |
| `data[].setAt` | string (ISO 8601) | Yes | When it was set, in UTC. |
| `nextCursor` | string or null | Yes | Send it as `cursor` for the next page. Null on the last page. |
| `total` | integer | Yes | How many rows the whole list has. |

### Example response

```json title="200"
{
  "data": [
    {
      "productId": "6410000000017",
      "name": "Oat milk 1 l",
      "category": "Dairy",
      "keepAt": 12,
      "neverStop": true,
      "reason": "Sold out every Saturday morning.",
      "setBy": "Anna Virtanen",
      "setAt": "2026-10-20T08:00:00.000Z"
    }
  ],
  "nextCursor": null,
  "total": 1
}
```

## Errors

A refusal is JSON with a `code`, a sentence in `error`, and a `requestId` when the fault is ours. Read the code, not the sentence. Every code is listed on [Errors](https://panlytics.net/developers/security/errors).

| Status | Code | When | What to do |
| --- | --- | --- | --- |
| 400 | `api.invalid` | A path id, a query parameter, a header or a body field is missing or not valid. `detail` names the field. | Read that endpoint in the API reference, correct the field and call again. |
| 401 | `api.key_missing` | The call had no Authorization header. | Send the key in the Authorization header as Bearer, then call again. |
| 401 | `api.key_refused` | The key is wrong, revoked, past its end, or its maker or company no longer allows it (developer mode off, the maker removed or switched off, or the maker's role lost the developer ability). | Ask the person who gave you the key to make a new one. |
| 401 | `api.wrong_key_kind` | This key does not open these endpoints. | Use the key these endpoints were made for, or ask the person who gave you the key. |
| 403 | `refused` | The key's maker may not do this here: their role lacks the ability, or the shop or category is outside their reach. | Ask the CEO for a role that allows it, or call it for a shop or category the role reaches. |
| 403 | `auth.not_fresh` | This step needs you to prove it is you. | Confirm your password or passkey, then try again. |
| 404 | `not_found.said` | Nothing with that id in the key's company. An id of another company answers the same. | Check the id. List the shop or category it belongs to and take the id from there. |
| 429 | `api.rate_limited` | The key made more than 120 calls in this minute. Wait the seconds in Retry-After. | Wait the seconds in Retry-After, then call again. |
| 500 | `server` | Something failed on our side. The answer carries a requestId to quote. | Try again in a minute; if it keeps happening, report it. |
| 503 | `developer.unavailable` | API keys are not set up on this deployment yet. | Report it, and we will switch them on. |