This statement explains what we commit to for the Rally & Roam API and MCP server, and what we do not. It is part of our API terms.

What we commit to

We run the API and MCP server on the same infrastructure as our website and monitor them in the same way, so a problem that affects one is noticed and worked on as a problem with the site.
We aim to announce planned maintenance that affects the API at least 48 hours ahead, by email to developer account owners and on the site's announcement banner. During maintenance the API answers 503 with Retry-After.
We keep the API behaving as its published API reference says. The reference is generated from the code, and automated tests call every documented endpoint and check the answer against it before every release.
We answer support email on UK working days and treat reports that the API is down, or that data is wrong in a way that could mislead people, before anything else.
We give the notice our deprecation and versioning policy promises before breaking changes.

What we do not promise

No uptime percentage. We do not yet measure availability over time in a way we could stand behind, so we do not publish an uptime figure or offer service credits. The status page shows live checks of each part as you load it.
No guaranteed response time. Most answers come quickly, but we do not promise a response time for any endpoint.
Open data as it is. Data from OpenStreetMap, Overture, Foursquare and other open sources is passed on as we receive it, credited, without a promise that it is complete or current.
Availability is live. Court availability can change between your check and a booking. A booking can still find the court taken (409 slot_taken).

If something goes wrong

Check the status page, then contact us with the X-Request-Id of an affected call. If an outage stops you using a paid plan for a long time, contact us: we will look at each case fairly, but there are no automatic credits. Nothing in this statement limits rights you have by law.

Changes to this statement

When we can commit to more, for example once we have measured availability for long enough to publish a figure, we will update this statement and the date at the top.

API service level statement