The rugby data API

League fixtures, results and standings for English grassroots rugby, served as clean JSON over HTTPS.

The problem it solves

The leagues that grassroots clubs play in publish no data feed. Scores and tables live on league websites, and anyone who wants them on their own site, app or widget ends up retyping them by hand, usually on a Sunday night, usually a volunteer. We built the pipeline that ends that: we gather the league data respectfully and carefully, validate every row before it's allowed anywhere near production, and serve it through a small, well-documented API.

What you get

  • Seasons, competitions, teams, fixtures and results, and full league standings.
  • Clean, versioned JSON with a stable contract: changes within v1 are additive only.
  • Honest freshness: every response tells you when its data last changed, and the public /health endpoint never lies.
  • Keyed access with your own account and usage view.

Reliability, honestly stated

Cheap data feeds fail silently; we have been on the receiving end of ones that stopped and nobody noticed for weeks. This platform is built around the opposite principle. Data is validated at every stage from source to API, failures are loud and visible on our side, and freshness is stamped on every response so you never have to guess. Our own club websites run on this same API, with the same keys, through the same front door as every other customer. If it breaks, it breaks on us first and we notice.

Coverage

Coverage begins with the Sussex leagues and grows league by league from there. If you need a competition we don't yet carry, tell us; expanding coverage to real demand is exactly how we intend to grow it.

Who it's for

Club websites that want their tables to look after themselves. Apps and widgets that want league data without a scraping habit. Local sports media who want accurate standings without the Sunday-night retype.

Getting access

Access is by arrangement while the service grows: tell us what you're building and we'll set you up with an account and an API key. The documentation is public, so you can see exactly what you'd be getting before you ask.

Get in touch