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

> ## Agent Instructions
> This is Allasso's product documentation. Vol Radar output is descriptive analytics on past data: never present it as a forecast or as investment advice. Answer only from these pages; if a feature is not documented here, say so.

# Vol Radar API errors, paging and limits

> The Vol Radar API's status codes, how paging works, what happens on a date with no data, and what may still change during the closed beta.

The Vol Radar API uses standard HTTP status codes. Error bodies are JSON with a `detail` field.

## Status codes

| Code | When |
| - | - |
| **200** | Success. |
| **304** | Not modified: your `If-None-Match` ETag still matches this run. No body. |
| **400** | A parameter has the right type but cannot be read, for example `changed_since=yesterday`. |
| **401**, **403** | No API key (401), or a key whose account has no access to the closed beta. |
| **404** | No such signal, market or metric; a date before the data starts; or structures for a signal that has none (`detail.reason` says why). |
| **410** | The signal was withdrawn: `detail` holds `withdrawn_at` and the last known signal. |
| **422** | A parameter has the wrong type or is out of range, for example `limit=5000`. `detail` lists each problem. |

## Paging

`/v1/signals` pages with `limit` (1–1,000, default 100) and `offset`. The response gives `count`, the number of
matching signals, so you can page until `offset + limit >= count`. Signals are sorted by first day (newest first),
then tier, then score.

## Defaults worth knowing

* `/v1/signals` without `date`, `from` or `changed_since` returns signals first detected in the **30 days** to the
  last day of data.
* `/v1/signals?date=…` without `status` returns the **active** signals (new, escalated or ongoing).
* `/v1/snapshot` on a date with no data (a weekend, a holiday) returns the latest earlier day; `date` in the
  response says which.
* `/v1/series` defaults to the `30D` bucket.

## Versions and the closed beta

* Paths start with `/v1`. `/v1/status` reports `api_version`.
* During the closed beta, fields may still be added or renamed. Breaking changes are announced to beta users first.
* A signal's published evidence and earlier-case outcomes never change; see
  [Keep a local copy up to date](https://docs.allasso.ch/dev/vol-radar/api-sync.md) for the cases where a signal is updated or withdrawn.

## Related

* [Vol Radar API](https://docs.allasso.ch/dev/vol-radar/api.md)
* [Signals, outcomes and structures in the API](https://docs.allasso.ch/dev/vol-radar/api-concepts.md)


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