Authentication - Quiver API

Send your API key in the Authorization header of every request:

curl https://api.quiverquant.com/beta/live/congresstrading \
  -H "Authorization: Bearer YOUR_API_KEY"

Authorization: Token YOUR_API_KEY also works. Both forms use the same key.

Where do I find my API key?

Your API key is on your dashboard, labelled Authorization Token. You get it when you create an account. It only returns data once you have an active plan; choose one on the pricing page. The same key works for the REST API and the MCP server.

How do I keep my API key safe?

Anyone with your key can use your plan and count against your rate limits.

Store the key in an environment variable or a secrets manager, not in your source code.
Don’t put the key in client-side code such as a browser app, where users can read it. Call the Quiver API from your server instead.
If your key is exposed, contact info@quiverquant.com.

What happens if authentication fails?

Status	Response	Cause
`401`	`{"detail": "Authentication credentials were not provided."}`	The `Authorization` header is missing, or it doesn’t start with `Bearer` or `Token`.
`401`	`{"detail": "Invalid token."}`	The key is wrong. Copy it again from your dashboard.
`403`	`{"detail": "Upgrade your subscription plan to access this dataset."}`	The key is valid, but your plan doesn’t include this dataset, or you don’t have an active plan. See Plans and data access.

See Errors for every status code the API returns.

Last modified on November 5, 2026