The Quiver API uses standard HTTP status codes. Error responses from API endpoints are JSON with a detail message, except where noted below.
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, where it’s labelled Authorization Token.
See Authentication.
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.
- you have no active plan, for example because your subscription ended. Your 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.
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 with the request URL and the time you sent it. Last modified on November 5, 2026
