DocumentationAPI v1
Documentation/Guides/Plans and windows
Guide

Plans and windows

What each plan reaches, and how a window shows in a response.

A plan decides two things: which endpoints a key reaches, and the window of dates it sees. The endpoint counts below are worked out by the same rule the API enforces.

PlanEndpointsWindowRateAllowance
Free key16Every free endpoint, on results at least seven days old60 a minute500 a day
Live44In-play and the last thirty days120 a minute250,000 a month
Archive43The whole archive, but nothing in play120 a minute250,000 a month
Complete44In-play and the whole archive180 a minute600,000 a month
Analyst52Everything, including the model endpoints240 a minute1,000,000 a month

How a window shows

Every response names its window in meta.window, so a missing week is never mistaken for a gap in the data. Asking for dates outside it answers 402 outside_window rather than an empty list that looks like nothing happened.

Changing plan

Your key stays the same. A new plan applies the moment payment confirms, with nothing to change in your code.