Build for the game.

Terms of use of the BuzzerBeater Public API

By registering an application or making a personal token you agree to these terms. They exist so that tools keep helping managers enjoy BuzzerBeater, and so that the game its community built is not copied.

You may

• Build tools that help managers with their own game: roster and training planners, scouting and market sheets, statistics for the leagues and national teams they follow, alerts, spreadsheets.
• Show a manager their own data in any form, and share aggregated league statistics.
• Charge for your tool, provided the game's data is not what you sell (see below).

You may not

1. Copy the game. No mirroring, scraping or bulk collection of BuzzerBeater data — through the API or around it — beyond what the managers using your tool look at themselves.
2. Build or feed another game, simulator or engine, or train, tune or evaluate models to reproduce BuzzerBeater's engine, ratings or economy.
3. Sell or hand over the data — raw or as datasets — or publish databases of other managers' players.
4. Keep or share other managers' player skills. Skills are private to the player's owner. A transfer-listed player's skills may be shown only to the manager who looked them up, only until skillsVisibleUntil (the auction's deadline). Do not store them past it, show them to your other users, or collect them into any history, database, "player card" or rating of other clubs' players.
5. Play for the manager. No automation of in-game actions by other means (bots, scripted browsers), no attempts to act through the API.
6. Get around the limits: several tokens, applications or accounts to multiply quotas, asking managers for their personal tokens, sharing one manager's token among users.
7. Mislead managers: pretend to be BuzzerBeater, ask for scopes you do not use, or hide what the tool does with their data.
8. Expose credentials: tokens and client secrets stay on your server or in the device's secure storage.

Transfer list and player skills: how we enforce it

A player's skills belong to his club. The transfer list shows them to buyers so they can bid, not so they can be collected.

• The API reveals a listed player's skills one at a time, only while his auction is open, and within small daily and 30-day caps per manager and per application.
• Every reveal is recorded — which manager, which application, which player, when — and kept for a year.
• If a collection, list, database or leak of player skills appears anywhere, we match its players against that record. It shows which accounts and applications revealed them, far above what scouting for one's own club needs.
• Those accounts are banned from the game, the applications are removed with all their tokens, and their developers lose access to the API. Spreading the collection across several accounts or applications does not hide it: each of them shows up.

Data and privacy

• You act for the manager who signed in. Use their data only for the tool they signed in to, keep it only as long as the tool needs it, and delete it when they revoke access or ask you to.
• Protect what you store as you would your own account. Tell us at once if tokens or data leak.
• Show a manager, somewhere they can find it, what your tool keeps and how to have it deleted.

Review, attribution and enforcement

• Applications start in development. To be opened to every manager, an application is reviewed by staff: describe what it does, link to it, and use the scopes you really need.
• Say on your tool that it uses data from BuzzerBeater and that it is not made by BuzzerBeater.
• We watch how applications use the API. An application or account that breaks these terms may be limited, suspended or removed, with its tokens revoked, and its developer's account restricted.
• The API is provided as it is. Endpoints may change within v1 only in compatible ways; breaking changes come with a new version and notice.