Professional padel data, as a feed.
FIP rankings, player identity, results and partnership evidence over plain HTTP. Read-only, versioned, and built so that asking the same question twice returns the same answer — forever.
Determinism is the product
Every response is taken at a cut-off you choose. A cut-off in the past will return byte-identical data in a year's time, which is what makes it possible to publish a hash of what you received and let anyone recompute it.
curl -H "Authorization: Bearer $KEY" \
"https://api.padelgod.io/v1/roster?asOf=2026-11-16T18:00:00Z&category=men"What you can ask for
/v1/rankings
The ranked field at any cut-off, drawn from append-only weekly snapshots.
/v1/roster
Rankings joined to identity: legal and display names, country, birthdate, coaches, photograph.
/v1/pairs
Who played with whom, how often, and when they last did. Evidence, not a verdict.
Coverage, including what is missing
A feed that only advertises its strengths costs you a week when you build on a field that comes back empty. These are the real numbers.
| Field | Men's top 200 | Women's top 200 | |
|---|---|---|---|
| Ranking, points, movement | 100% | 100% | complete |
| Name, country, birthdate | 99% | 100% | complete |
| Coaches | 98% | 99% | complete |
| Photograph | 64% | 54% | partial |
| Partnership evidence | 93% | 92% | complete |
| Per-player Elo | 0% | 0% | not yet |
Two decisions worth knowing before you build
Cut-offs carry a timezone
asOf must include an explicit offset. Without that rule the same cut-off
would mean different instants depending on where the server runs, and a published hash
would prove nothing.
Pairs ship evidence, not verdicts
We count shared main-draw matches rather than naming a partner. The threshold is a policy of whoever publishes it — and a single-partner rule measured only 81% symmetric against real data.