How Sportscanner works
One search over nineteen booking systems that never show each other's courts, and why scraping them takes more than firing off a query.
Published: ·5 min read
Courts in London aren't scarce. They're scattered.
Say it's Thursday evening, you live near Canary Wharf and you want to play something tonight. Within two miles of you there are badminton, padel, pickleball and tennis courts on six different booking systems. So you open Be Well's site for Poplar, Southwark Leisure's for Canada Water and, if you'd settle for padel, Playtomic and Padel Mates as well. Each one shows its own courts and nobody else's, with its own date picker and its own way of saying "full". By the time you've checked the fourth, the 7pm slot you liked on the first one has gone.
That's the question that started Sportscanner in 2023: why does booking a court in London take ten websites? The answer is that leisure trusts, councils, private padel clubs and park tennis courts each run their own booking system, and none of them has any reason to show you somebody else's courts. But you don't care who runs the building. You care whether there's a court, how far away it is and what it costs.
So Sportscanner is one search over all of them. You give it a postcode, a sport and a date, and it shows every bookable slot nearby, with a link to book it on the operator's own site. It doesn't take the booking or the money. It just does the comparison you'd otherwise do by hand, across 251 venues and five sports. A bit over 800 players use it now, almost all of them through word of mouth (and some shameless Reddit posting).
The value is speed in a race. The good slots, the 7pm courts on a weeknight, go to whoever happens to look at the right moment. Sportscanner doesn't create a single extra court. It just shortens the race for the ones there are.
Building it sounds easy. Ask each site what's free, show the answers. Scraping looks like firing off a query. In practice you're a guest on nineteen systems that were never built for you, and each one finds its own way to make that hard.
The first problem is that they all speak differently. One operator has two versions of its booking system with venues moving between them on their own schedule. Another hands you every venue for a date in one go. One has no API at all, just a web page. If that variety leaks into the product, every new operator means changing the product. So it stays at the edge: each operator gets a small translator that turns its answer into one common shape (venue, sport, time, price, spaces left, booking link), and nothing after that ever knows where a slot came from. Where an operator doesn't publish prices, Sportscanner estimates one from the same venue's other slots and puts a tilde in front of it, so a guess never passes as a quote.
The second problem is manners. One refresh means several hundred requests to a big operator. Fire them all at once and their servers start dropping them, and some operators block whole ranges of cloud servers or check whether the visitor looks like a real browser. So Sportscanner asks each operator only so many questions at a time, and when one is clearly down, it stops asking instead of hammering a site that isn't going to answer.
The third problem is the one users actually feel: freshness. A slot is a snapshot, and it starts going stale the moment you read it. Worse, when somebody books a court, the operator doesn't tell you. The slot just isn't there the next time you look. So everything gets checked again every 15 minutes, anything that has disappeared is marked as gone rather than left on screen, and results say how recently they were checked. Stale data is worse than none, because the first time someone turns up for a court that was booked hours ago is the last time they trust you.
One rule sits over all of this. Sportscanner only reads availability that anyone can see without logging in. If an operator keeps its timetable behind an account, even a free one, it's out of scope. That's the right trade: a product that depends on getting round somebody's login is one email away from not existing.