Rate limits and pagination

​

How do the limits work?

• Limits are shared within a group. All endpoints with the same limit draw from one allowance. For example, the endpoints limited to 200 requests per hour share a single 200-per-hour allowance, so 150 calls to one leaves 50 for the rest.
• Each group is separate. Using up the 5-per-hour bulk allowance doesn’t affect your per-minute endpoints.
• Limits are per account. Every request made with your API key counts, whichever machine sends it.

​

What happens when I exceed a limit?

{"detail": "Request was throttled. Expected available in 42 seconds."}

import os
import time

import requests

HEADERS = {"Authorization": f"Bearer {os.environ['QUIVER_API_KEY']}"}


def get(url, **params):
    while True:
        response = requests.get(url, headers=HEADERS, params=params, timeout=60)
        if response.status_code != 429:
            response.raise_for_status()
            return response.json()
        time.sleep(int(response.headers.get("Retry-After", "60")))

​

How do I get all the results?

• Use bulk endpoints for full history. Bulk endpoints such as Bulk Congress Trading return a dataset’s full history in a few large responses. Their limit is 5 requests per hour, so request large pages rather than many small ones.
• Page through paginated endpoints. Endpoints that paginate take a page parameter (starting at 1) and a page_size parameter. Keep requesting the next page until a page comes back with fewer results than page_size. Each endpoint’s reference page lists its default and maximum page size.
• Prefer one broad request over many narrow ones. Looping a per-ticker endpoint over hundreds of tickers uses up a 10-per-minute allowance quickly. If a live or bulk endpoint covers every ticker, use it instead and filter the results yourself.

​

Rate limit for each endpoint

​

100 requests per minute

​

10 requests per minute

​

200 requests per hour

​

5 requests per hour