Community tools, training planners, league statistics. Everything you need to connect your idea to BuzzerBeater.
Migrating from bbapi
The legacy bbapi.buzzerbeater.com served XML pages to a session opened with the manager's login name and
read-only access code. The public API keeps the same idea — read the game for a manager — and changes how.
What changes
bbapi
Public API v1
XML, one RelaxNG schema
JSON, OpenAPI document at /v1/public.json
login.aspx?login=…&code=… in the URL, then a cookie
OAuth 2.0 with PKCE, or a personal token; always in the Authorization header
The access code gives everything the account sees
The manager chooses scopes, and can revoke each tool on its own
Integer ids
UUIDs (strings)
secondteam=1 to switch team
Every club and national team the manager runs is listed by /v1/me; pass its id
No documented limits
Per-minute, daily and breadth limits, reported in headers
Errors as <error message="…"/> with HTTP 200
HTTP status codes plus {"error":{"code","description"}}
Legacy ids do not carry over: the new game is a new world. A tool that stored legacy ids should start its
data afresh.
