What you can build with the data, and the few things you cannot.
Build whatever you like on the data, including commercial products, and show it to your users. Do not share your key, do not run several free accounts to dodge the limits, and do not republish the archive in bulk as a competing feed. Break these badly and the account gets suspended.
Build applications, dashboards, models, research and content on the data, including commercial products you charge for.
Show data from the API to your own users, in your own interface.
Store what you need in your own systems, and keep it after you cancel.
Attribution is not required. It is appreciated, and a link back helps.
Your key is yours. Do not publish it, commit it to a public repository, or embed it in a mobile or browser application where anyone can read it. Call the API from your own server instead.
Calls made with your key count against your limits and count as made by you. If it leaks, rotate it from your account.
The line is between building on the data and reselling the data itself.
Serving match data inside your own product is fine, even at scale. Systematically pulling the archive down and offering it as a data feed, dataset or API that competes with this one is not.
If you are unsure which side of that line your idea sits on, ask us first. We would rather say yes in advance than close an account later.
Do not hold multiple free accounts to multiply the free allowance, and do not rotate keys or addresses to avoid rate limits.
If you need more than a plan allows, tell us. A higher plan or an arrangement is nearly always cheaper for you than the effort of evading the limit.
The API is the supported way to get the data. Please do not scrape the HTML pages, the Lab or the documentation, and do not run automated traffic against them.
You are responsible for the law where you and your users are. Gambling is regulated differently in every jurisdiction, and if you build something in that space, complying with those rules is your responsibility, not ours.
Do not use the service to break the law, to infringe anyone else's rights, or to attack, overload or probe our systems or anyone else's.
Where it is reasonable, we get in touch first and give you a chance to fix it. For anything that threatens the service or is plainly deliberate, we may suspend the key immediately.
Repeated or serious breaches end the account. No refund is due in that case, in line with the refund policy.
If you think we have got it wrong, reply to the notice — a real person reads it.