Courts - an index of tennis courts around the world

Courts is an open index of tennis courts around the world. At Matcha Tennis, our goal is to be the fastest way to play.

Today, one of the biggest frustrations for players is simply finding and booking a court. Reservation systems are fragmented, legacy software creates poor user experiences, and important details like court rules, surfaces, availability, and conditions are often difficult to access.

We’re building a universal court index to make courts more discoverable, modernize the booking experience, and help more people spend less time off court and more time playing.

If you love tennis, we invite you to join us in making the sport more accessible to everyone.

Contents

• Specification
  • MRN - Matcha Resource Name
  • Slot - A bookable unit
• Data
• API
• Clients
• Contributing

Specification

MRN - Matcha Resource Name

An MRN uniquely identifies a tennis court across every booking platform.

platform:organization:resource

Segment	Description
platform	Booking platform (e.g. activenet, rec)
organization	Venue or site within the platform
resource	Slash-delimited path to the specific court

Example:

rec:sfrecpark:location/12/court/3

Slot - A bookable unit

A slot is a bookable time window on a court, identified by that court's MRN.

Field	Description
start	UTC epoch, in milliseconds
duration	Length of the window, in milliseconds

In availability listings a slot also carries a state of RESERVABLE or EXPIRED.

Data

Places are grouped by provider - the platform:organization pair - under providers/, one directory per provider holding a places.json. Each platform's reservation sites, public endpoints, and MRN formats are documented under platforms/.

Provider	Platform	Location
providers/activenet-seattle	ActiveNet	Seattle, WA
providers/activenet-shorelinewa	ActiveNet	Shoreline, WA
providers/civicrec-wa-bellevue	CivicRec	Bellevue, WA
providers/clubautomation-edgebrook	ClubAutomation	Bellevue, WA
providers/clubautomation-tcsp	ClubAutomation	Seattle, WA
providers/courtreserve-12465	CourtReserve	San Francisco, CA
providers/courtreserve-6689	CourtReserve	Woodinville, WA
providers/courtreserve-7306	CourtReserve	Bellevue, WA
providers/courtreserve-17764	CourtReserve	Bellevue, WA
providers/rec-sf-rec-park	Rec	San Francisco, CA

API

https://api.matchatennis.com/ implements the Courts specification.

• All requests and responses are JSON.
• Errors return { "error": "<message>" } with a 4xx/5xx status.
• List endpoints are cursor-paginated: pass ?cursor=<value> and read the next cursor from the response.

Method	Path	Description
GET	/places	List all places (cursor-paginated)
GET	/places/{placeId}	Get a single place

GET /places
GET /places/97dbdd4823

Clients

1. Matcha Tennis iOS
2. Matcha Tennis Web

Contributing

There are a few ways to help grow the index:

1. Update a place - fix or improve an existing court by editing its provider's providers/<platform>-<organization>/places.json, e.g. coordinates, tags, or court names.
2. Add new places - add courts for a new venue. Extend an existing provider's places.json, or create a new providers/<platform>-<organization>/places.json for a provider that isn't listed yet. See platforms/ for how to discover each platform's params.
3. Add a new platform - when a venue books through a platform not yet in platforms/, document it: investigate its portal and public endpoints, define its MRN format, and add a platforms/<platform>.md following the structure of the existing docs. Then add places under it.

After editing files under providers/, run bun run build to validate the data and regenerate INDEX.md.

Questions or ideas? Start a discussion at matchatennis.com/support.