Acceptance of terms
[Explain how and when these terms are accepted, for example on account creation, API key generation or first API call, and who the agreement is between.]
[State who may accept on behalf of an organisation and that they must have authority to do so.]
- Provider
- [Company legal name]
- Company number
- [Company registration number]
- Registered address
- [Registered company address]
Definitions
[Define the key terms used throughout, for example “API”, “API key”, “Customer”, “Data”, “Documentation”, “Plan”, “Request” and “Service”.]
[Keep the definitions consistent with the Pricing page and the API documentation.]
Accounts and API keys
[Describe who may use the API and account eligibility requirements, such as minimum age or business use, and the information required to register.]
[Explain the customer’s responsibility for keeping API keys confidential and for all activity under their keys, and how to rotate or revoke a compromised key.]
Plans, billing and renewals
[Describe the available plans and refer to the current prices on the Pricing page.]
[Explain billing cycles (monthly or yearly), automatic renewal, upgrades and downgrades, proration, taxes, failed payments and the refund policy.]
[State how price changes are communicated and how much notice customers receive.]
Usage limits and fair use
[Explain request quotas and rate limits per plan, how usage is measured, and what happens when a limit is reached, for example throttling, HTTP 429 responses, overage charges or an upgrade prompt.]
[Describe the fair-use principles that apply, including caching expectations and excessive polling.]
Acceptable use
[List prohibited uses, for example sharing API keys, reselling or redistributing raw data feeds, circumventing rate limits, scraping, reverse engineering, and any unlawful, harmful or infringing use.]
[Note any restrictions on use in betting or gambling products, if applicable, and any regulatory requirements customers must meet.]
Data licence and attribution
[Describe the licence granted to use the data: scope, permitted uses per plan, whether public display and commercial use are allowed, and limits on redistribution and storage.]
[Specify any attribution requirements (wording, placement, logo use) and whether they differ by plan.]
[Explain what happens to stored or cached data when a subscription ends.]
Customer content
[Define customer content, such as data or materials a customer submits to the service, and confirm who owns it.]
[Describe the limited rights needed to host and process that content to run the service, and refer to the Privacy Policy for personal information.]
Service availability and support
[Describe target availability, planned maintenance and how incidents are communicated, for example on the API Status page.]
[Explain support channels and response times by plan, and whether a service level agreement (SLA) or service credits apply, for example to Enterprise customers.]
Changes to the service and API versioning
[Explain how the API is versioned, what counts as a breaking change, and the notice period and deprecation process before a version is retired.]
[Describe how changes are announced, for example in the Changelog and by email.]
Third-party data sources
[Explain that some data may come from third-party sources, officials or partners, and any limits on accuracy, completeness or timeliness that follow from this.]
[Describe any additional terms from data providers that pass through to customers.]
Intellectual property
[State who owns the service, API, documentation, data compilations, trademarks and logos, and that no rights are granted beyond those expressly stated.]
[Explain how feedback and suggestions from customers may be used.]
Confidentiality
[Define confidential information, each party’s obligations to protect it, permitted disclosures and how long the obligations last.]
Warranties and disclaimers
[Describe any warranties given and the extent to which the service and data are provided “as is”, within what applicable law allows.]
[Address the accuracy of live and historical data and the customer’s responsibility for decisions made using it.]
Limitation of liability
[Set out any limits and exclusions of liability, including any cap and the types of loss excluded, in line with applicable law.]
[List the liabilities that cannot be limited under the governing law.]
Indemnification
[Describe any indemnities each party gives, for example for third-party claims arising from misuse of the service or infringement, and the process for handling such claims.]
Suspension and termination
[Explain when access may be suspended or terminated, for example non-payment, breach of these terms or a security risk, and what notice is given.]
[Describe how customers can cancel, what happens to data and outstanding fees on termination, and which sections continue to apply afterwards.]
Governing law and disputes
[Name the governing law and the courts or dispute-resolution process that apply, including any informal resolution step before formal proceedings.]
- Governing law
- [Governing law / jurisdiction]
Changes to these terms
[Explain how these terms may be updated, how customers are notified (for example by email or an in-app notice), the notice period and when changes take effect.]
[Note that the effective date at the top of this page identifies the current version.]
Contact
[Explain how to contact the company about these terms, including where formal legal notices must be sent.]
- Company
- [Company legal name]
- Registered address
- [Registered company address]
- Company number
- [Company registration number]
- Legal enquiries
- [legal@yourdomain.com]