Fair use and changes

Anyone can use the read-only public API: a school project, a fan site, a bot, a tool of your own. There are no keys and no fees. In return, we ask you to follow a few simple rules so that it stays free and safe for the children who play on Bazoodle.

Fair use

Please do

• Be gentle. Stay within the rate limits, cache responses and wait when you receive 429.
• Say who you are. Send a descriptive User-Agent with a way to reach you.
• Give credit. Say that the games come from Bazoodle and link to the game’s page on https://bazoodle.com/game/<id> so people can play it where it was made.
• Escape text. Titles and descriptions are written by creators. Show them as text, never as HTML.
• Keep it kid-safe. Everything the API returns is kid-friendly. Do not put it next to adult content, chat or links that lead children somewhere that is not.

Please do not

• Do not look for people. Names in responses are made-up usernames. Do not try to find out who a player is, collect names into profiles, contact players or track a person.
• Do not copy games. The API tells you about games; it does not give you the right to copy a game’s pictures, text or files into another product. Link to the game instead.
• Do not hammer the servers. No scraping loops and no running many addresses to get around limits.
• Do not pretend to be Bazoodle. Do not use the Bazoodle name or logo in a way that suggests we made or approved your tool.
• Do not use it to break Bazoodle’s rules. The Community Rules and Terms apply to anything built on Bazoodle.

We may slow down or block addresses that cause trouble, and we may change or remove parts of the API at any time. If your tool has a bug that sends us too many requests, we will try to write to the contact in your User-Agent first.

Versions

The address contains the API version: /v1. A change that could break a tool that follows these docs (a field renamed or removed, a different meaning) will come as a new version at /v2, and /v1 will keep working for a while after that, with the date written here. Adding fields, endpoints and values is not a new version. Addresses without a version are the website’s own and are not covered by this promise.

Stability and changes

Bazoodle is young, and so is its API.

What	What to expect
Endpoints in these docs, their query parameters, the names and meaning of response fields	We try to keep them stable.
New fields in a response	Can appear without warning. Ignore fields you do not recognise.
New values in fields that list choices (new tags, a new status)	Show or ignore an unknown value; do not crash on it.
Limits and cache times (page sizes, rate limits, max-age)	Are settings and can change. Read the headers and Retry-After instead of hard-coding numbers.
Endpoints themselves	Can be removed or limited if they are abused or if Bazoodle’s design changes. There are no keys, so we cannot email you: these docs are where changes are written down.

Building something that lasts

• Parse JSON into a structure that tolerates extra fields, and treat null as a normal value.
• Show a friendly message when the API answers an error or is slow; Status tells you whether the problem is on our side.
• Keep the API address in one place so it is easy to change, and re-read these docs before you ship an update.

Anything not described in these docs is not part of the public API, even if it happens to answer a request today. In particular, do not rely on routes the Bazoodle website calls for signed-in players: they are private, they change with the site, and calling them from other tools is not allowed.

If a field is unclear or something you need is missing, write to help@bazoodle.com. The docs are written to match the running API; if you find a place where they do not, we want to fix it.