These terms apply when you use the Rally & Roam developer API: the endpoints under /partner-api/v1, the API keys, the webhooks and the developer dashboard. They sit alongside our terms of use and our privacy policy. If you use the API for a business, you accept these terms for that business and confirm you have the authority to do so.

Your account and keys

Every developer account starts on the free sandbox plan with a test key. Test keys read real data and check bookings fully, but never store a booking, email anyone or charge anything.
Live keys need a paid plan and two-factor sign-in on your account. Keep keys secret: anyone with a key can use your allowance. We show each key once; if one leaks, rotate or revoke it on the dashboard straight away.
One account per person or business. Do not share keys between unrelated businesses or resell access to the API itself.

Plans, limits and fair use

Each plan sets a monthly allowance of calls, a limit per minute and the endpoint groups it opens. The free sandbox plan allows 1,000 calls a month and 10 a minute, with test keys only. The current paid plans, their allowances and prices are on the developer page, and the price is always shown before you pay.
Past the monthly allowance, calls are refused with quota_exceeded until the allowance resets, unless your plan includes overage. Overage is charged per 1,000 calls (part thousands round up) and reported to our billing provider once a day.
Do not try to get around the limits, for example with several accounts, and do not use the API to copy our whole catalogue for a competing directory. We may slow down or pause keys that put the service at risk, and we will tell you why.

Partner integrations

Some partners, such as travel companies, are set up by our team directly rather than through the developer dashboard. They get their own keys, endpoints for itineraries and bookings, webhooks and a booking widget they can place on their own site, and may earn a share of revenue that we agree with them. The widget sets no cookies. These terms apply to those partners too, together with anything else we agree with them in writing.

The data, and the credit it needs

Every field in an answer is tagged with where it came from (sources), and every item carries the credits for those sources (attribution). We only serve data we are allowed to license to you; our insight reports and data licensing page and data sources page give more detail:

Our own data: bookings and court availability, reviews and ratings, level ratings, destinations and events we write, and itineraries built from them.
What clubs and coaches give us when they join or claim their listing.
Open data whose licence allows it, with credit: Overture Maps (CDLA Permissive 2.0), Foursquare OS Places (Apache 2.0), the Colombia padel club census by Comando Construcciones SAS (CC BY 4.0) and OpenStreetMap (Open Database Licence 1.0).

When you show data to people, show the credits in attribution next to it or on a page linked from it. Fields from OpenStreetMap are under the Open Database Licence: if you publish a database built from them, you must offer it under the same licence and keep the credit "© OpenStreetMap contributors". Our club database itself also stays free to download under that licence.

We do not serve text from Wikivoyage, descriptions taken from club websites, photos from Wikimedia Commons or Mapillary, weather and climate data, or data from Google or other paid sources, and you must not ask us to.

What you may do with it

Show clubs, coaches, events and availability in your own product, and book courts for your guests through the booking endpoints, within your plan.
Keep a copy of answers for up to 30 days to make your product faster. Availability changes all the time, so check it again before you show it as free.
Do not suggest that Rally & Roam, a club or a coach endorses your product, and do not use the data to contact players, clubs or coaches for marketing they have not agreed to.

The MCP server and AI assistants

Our MCP server at /mcp offers the API's read endpoints as tools for AI assistants and code editors. Everything in these terms applies to it: each tool call counts as one call against your key and plan, and the data and credits are the same as the API's.
You can connect an app to your account with OAuth instead of giving it a key. You choose which of your keys it acts as, and you are responsible for what it does with your access. You can disconnect it at any time on the developer dashboard.
When an assistant shows our data to someone, the attribution notices in the answer still apply. Do not configure an assistant to hide them or to present our data as its own.
AI assistants can make mistakes with the data they are given. You are responsible for checking what your product tells people, especially prices, times and availability, which change.

Bookings made through the API

Bookings you make are held as requests until the guest pays us directly, and our booking terms apply between the guest, the club and us. You must have the guest's permission to send us their name and email address.

Billing

Paid plans are billed monthly in advance through Stripe. Invoices, card details, plan changes and cancelling are in the billing portal on your dashboard. The price, and any VAT, is shown before you pay.
If a payment fails, live keys keep working for 7 days while the card is retried or replaced. After that, live keys are switched off until a payment goes through; test keys keep working.
If you cancel, your plan runs to the end of the period you paid for and then moves back to the free sandbox. We do not refund part months, except where the law says we must.
We may change plans or prices with at least 30 days' notice by email. A price change starts at your next billing period after the notice ends.

Webhooks

Webhooks are signed with a secret shown once when you add the endpoint. Check the signature on every request. We retry failed deliveries a few times and then stop; webhooks are a convenience, not a guarantee, so check important bookings with the API too.

Changes to the API

We keep version 1 stable: we may add endpoints, fields and error codes, but we will not remove or rename them without at least 90 days' notice by email, unless we have to for security or legal reasons.

Liability

We work hard to keep the API available and the data accurate, but we provide it as it is. Open data and listings can be out of date. Nothing in these terms limits liability that cannot be limited by law. Otherwise our total liability to you in any 12 months is limited to what you paid us for the API in that time.

Ending

You can cancel a paid plan at any time in the billing portal, and close your developer account by emailing us. We may suspend or close an account that breaks these terms, after telling you what is wrong and, where we reasonably can, giving you time to put it right.

These policies form part of these terms and explain parts of them in more detail: API acceptable use, rate limits and fair use, data licensing and attribution, deprecation and versioning, privacy for API and MCP use and our service level statement. If one of them and these terms disagree, these terms win.

Contact

Questions about these terms or the API: use the Help centre once you are signed in.

These terms are governed by the law of England and Wales.

API terms