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

> ## Agent Instructions
> Quiver Quantitative API: base URL https://api.quiverquant.com, endpoints under /beta/. Authenticate every request with the header `Authorization: Bearer <API key>`. Keys are on https://api.quiverquant.com/dashboard/ after subscribing at https://api.quiverquant.com/pricing/.
> AI agents can use the Quiver MCP server at https://mcp.quiverquant.com/ (streamable HTTP; OAuth sign-in, or the API key as a Bearer token). Setup: https://api.quiverquant.com/docs/mcp-server.
> Each dataset needs a plan (https://api.quiverquant.com/docs/plans-and-access) and each endpoint has a per-account rate limit (https://api.quiverquant.com/docs/rate-limits).

# Errors

> What each Quiver API status code means, with example responses and how to fix the request.

The Quiver API uses standard HTTP status codes. Error responses from API endpoints are JSON with a `detail` message, except where noted below.

| Status | Meaning | Example response |
| - | - | - |
| `200` | Success. | The data you asked for. |
| `401` | The API key is missing or wrong. | `{"detail": "Invalid token."}` |
| `403` | Your plan doesn't include this dataset, or you have no active plan. | `{"detail": "Upgrade your subscription plan to access this dataset."}` |
| `404` | The endpoint doesn't exist. | An HTML "Not Found" page, not JSON. |
| `429` | You exceeded the endpoint's rate limit. | `{"detail": "Request was throttled. Expected available in 42 seconds."}` |
| `500` | The request failed on our side, or a very broad query ran past the 60-second time limit. | Varies. |

## 401: how do I fix authentication errors?

* `"Authentication credentials were not provided."` means the request had no `Authorization` header, or the header didn't start with `Bearer` or `Token`. Send `Authorization: Bearer YOUR_API_KEY`.
* `"Invalid token."` means the key is wrong. Copy it again from your [dashboard](https://api.quiverquant.com/dashboard/), where it's labelled **Authorization Token**.

See [Authentication](/docs/authentication.md).

## 403: why can't I access a dataset?

Your key is valid, but your account can't use this endpoint. Either:

* the dataset is on a higher plan. For example, insider trading and 13F holdings need the Trader plan. See [Plans and data access](/docs/plans-and-access.md).
* you have no active plan, for example because your subscription ended. Your [dashboard](https://api.quiverquant.com/dashboard/) shows your plan and its status.

## 404: why is the endpoint not found?

Check the path against the API reference. Paths start with `/beta/`, and per-ticker endpoints take the ticker in the path, for example `/beta/historical/congresstrading/AAPL`.

## 429: what should I do when I'm rate limited?

Wait the number of seconds in the `Retry-After` response header, then retry. To avoid limits, prefer bulk and live endpoints over looping per-ticker endpoints. See [Rate limits and pagination](/docs/rate-limits.md).

## 500: what if the request fails or times out?

Retry once after a short wait. If the request is broad, such as Live SEC13F with no `ticker`, `owner` or `date` filter, narrow it with filters or a smaller `page_size` so it finishes within the 60-second limit. If an error keeps happening, email [info@quiverquant.com](mailto:info@quiverquant.com) with the request URL and the time you sent it.


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