CourtNow Data API
Live, normalized padel court availability for all of Prague. Every booking platform sits behind one schema, with prices, freshness and booking links. One integration instead of six.
{
"venue_id": "isport:forpadel",
"court_id": "isport:forpadel:1",
"start_ts": "2026-08-26T17:00:00+02:00",
"end_ts": "2026-08-26T17:30:00+02:00",
"status": "free",
"price": 340,
"currency": "CZK",
"free_courts": null,
"deep_link": "https://forpadel.isportsystem.cz/",
"source": "isport",
"fetched_at": "2026-08-26T16:58:12+02:00"
}What it does
- One normalized feed across every Prague platform, from iSportSystem, reenio, CourtyONE, PadelOS and Bookaball to clubs’ own sites. All behind a single schema.
- Every read carries a timestamp. Each slot says when we last checked it, so you never show a court that is already taken.
- Full detail on every slot: price, court, surface, length and a link to book. Not just free or busy.
- A growing archive of how availability and prices change by hour, day and venue.
Who it’s for
- Racket sport apps that want Prague coverage without building six scrapers.
- Clubs and operators that want to compare their demand, pricing and usage against the market.
- Media, tourism and concierge services adding a “find a court now” feature to their product.
- Analysts and researchers studying demand for sports facilities in Czechia.
What it solves
- Fragmentation. Every platform has a different API, or none at all. We did the integration once, so you do not have to.
- Trust. We check how fresh the data is, so an old slot is never shown as free.
- Comparability. One schema, one currency field, one time zone. It drops straight into your product.
- Speed. One endpoint instead of months spent reverse engineering each platform.
Building something that needs court data?
Tell us what you are making and how you would use the feed. We will set you up during the beta.