API terms
Plain terms for a read-only census API. If something here is unclear, ask through support before you build on it.
What you may build
Anything, including something you charge for. Bots, dashboards, alliance tools, spreadsheets, a paid product — all fine. You do not need permission and you do not owe a revenue share.
What you may not do
- Re-serve this data as a feed, a mirror or a competing API. Query it for your own product; do not become a second source of it.
- Resell raw records, in bulk or otherwise. Sell what you built; do not sell what you fetched.
- Share your key. It identifies your account and every request it makes counts against you.
- Work around a limit — with extra accounts, extra keys, or by presenting no key at all.
Attribution
Say where the data comes from somewhere a reader can find it, and link back. A line in an about page or a help command is enough.
Limits are operating values
Published limits are what we are running today, not an entitlement. They can change, up or down, without notice. Design for being refused: read the error code and the Retry-After header, and back off rather than retrying in a loop.
The data itself
It is observational, incomplete and sometimes stale. It is offered as it is, with no warranty of accuracy, completeness or availability, and it may be wrong when your users most want it to be right.
Ending it
You can revoke a key whenever you like. We can refuse a key that breaks these terms, harms the service or harms the people in the data — normally after asking you first, and immediately if it cannot wait.
Changes
These terms can change. Continuing to use a key after a change accepts it.
Questions
Ask through support. If you are about to build something substantial, ask first — it is cheaper than finding out afterwards.