Developer Terms

• Adults with a club account. Keys are created by a signed-in parent account, so you're 18 or older and you've agreed to the club terms.
• You're responsible for what your key does. Keep it secret. If it leaks, revoke it on the developers page and make a new one. Don't share a key between unrelated projects or people.
• Build for readers. Practice tools, family screens, classroom and team helpers, bots that ask a question a day: all welcome. If you want to charge money for something built on the API, write to us first at [email protected].

The daily question can be tuned to a reader or a team by their code. A code is a key to that child's reading, so:

• Only use codes you were given on purpose by that reader's parent or that team's coach, for the thing they gave it to you for.
• Treat codes like passwords. Store them encrypted or not at all. Send them to the API only in the X-Reader-Code and X-Team-Code headers, never in a URL, and never in client-side code for the public.
• Show a reader's information only to their own family or team. The API returns display names and reading progress, nothing else, and your app shouldn't add to that.
• Don't collect personal information from children. OBOB.dog never asks kids for their name, email or school, and an app built on it must not either (see COPPA). If your app has its own accounts for kids, that's on you to do lawfully.
• A parent can cut you off by replacing their reader's login code, and a coach by regenerating the team code. Expect it and handle it gracefully.

• Credit the writers. Questions come from OBOB volunteers, libraries and club members. Every question carries its source; show the source name near the question, and say somewhere that your questions come from OBOB.dog.
• Use it live, don't copy it out. Cache what you need to make your app quick, but don't crawl the API to build your own question bank, re-publish the questions in bulk, or sell them.
• Book details (titles, authors, covers, descriptions) belong to their publishers and authors. We pass them along for showing readers what to read; use them the same way.
• Fix what you find. If a question looks wrong, tell us at [email protected] so a reviewer can fix it for everyone.

• Stay inside the rate limit and back off when you get a 429. The daily question is the same all day; ask once and keep it.
• Don't pretend to be us. Your app is yours: don't use the OBOB.dog name, Rosie or our wordmark in a way that suggests we made or endorse it. "Questions from OBOB.dog" is fine and appreciated.
• OBOB.dog isn't the official Oregon Battle of the Books. Don't suggest otherwise.

• It's early. The API is new and may change. We'll try to give notice for breaking changes on the developers page, but we can't promise it will always be available or always be right. It's provided as is, without warranty.
• We can revoke keys that break these terms, put readers at risk or load the site unreasonably, and we can close the API altogether if we have to.
• We may change these terms. When we do, you'll be asked to agree to the new version before your keys keep working.

Questions, ideas or a thing you built? We'd like to see it: [email protected].