padel.how API — Machine-Readable JSON Endpoints

Overview

padel.how exposes structured, machine-readable data for all published reviews and equipment categories. All endpoints are static JSON files served from the same origin as the HTML pages. No authentication, API key, or rate limit applies.

Aggregate JSON files include a generated field (ISO 8601 date) so consumers can detect stale caches. Per-slug detail JSON keeps the same stable schema but may omit generated. URLs in JSON responses are absolute https://padel.how/… paths where a URL field is present.

For AI agent discovery, see llms.txt (compact) and llms-full.txt (expanded agent context).

Racket endpoints

Endpoint	Description	Items
`/rackets.json`	Aggregate of all racket reviews. Fields: name, slug, url, brand, year, score, shape, thickness_mm, weight_g, balance_cm, face_material, core, surface, player_level, play_style, scores (10 categories), gender, junior.	115
`/rackets/{slug}.json`	Full per-racket detail. Same fields as aggregate plus verdict text, FAQ array, compared_to slugs. Example: `/rackets/nox-at10-18k-2026-review.json`	115 files
`/data/rackets.json`	Locale-neutral rackets aggregate (mirrors /rackets.json).	115

Racket score categories (0–10 each, sum = /100 score): maneuverability, net_performance, control, defensive_output, off_center_stability, sweet_spot, spin_generation, power_ceiling, power_accessibility, comfort.

Methodology: padel.how/equipment/racket/methodology/

Shoe endpoints

Endpoint	Description	Items
`/shoes.json`	Aggregate of all padel shoe reviews. Fields: name, slug, url, brand, score, price_band, player_level, best_for, scores (7 categories).	64
`/data/shoes/{slug}.json`	Full per-shoe detail including specs object and scores. Example: `/data/shoes/babolat-premura-3-review.json`	64 files
`/equipment/shoes.json`	Legacy shoes aggregate (same data, maintained for backwards compatibility).	64

Shoe score categories (0–10 each): grip, lateral_support, cushioning, breathability, durability, fit_security, value.

Shoe review hub: padel.how/equipment/shoes/ — Methodology: padel.how/equipment/shoes/methodology/

Overgrip endpoints

Endpoint	Description	Items
`/overgrips.json`	Aggregate of all published overgrip reviews. Fields: name, slug, url, brand, score, best_for, scores (6 categories).	4
`/data/overgrips/{slug}.json`	Full per-overgrip detail including declared specs, measured weight/length, moisture absorption data. Example: `/data/overgrips/head-xtremesoft-overgrip-review.json`	4 files

Overgrip score categories (0–10 each): feel, moisture_absorption, tackiness, durability, weight_impact, value.

Overgrip review hub: padel.how/equipment/overgrip/ — Reviews library: padel.how/equipment/overgrip/reviews/ — Methodology: padel.how/equipment/overgrip/methodology/

Search indexes

Endpoint	Description
`/data/search-index.{locale}.json`	Lightweight per-locale search index used by on-site search. Locales: `en`, `fr`, `de`, `it`, `es`, `pt`, `se`, `no`, `dk`. Example: `/data/search-index.en.json`
`/data/rackets.{locale}.json`	Locale-specific racket catalog data. Locales: `fr`, `de`, `it`, `es`, `pt`, `se`, `no`, `dk`. English uses `/data/rackets.json`.
`/data/equipment.json`	Combined equipment aggregate: shoes (64), balls (7), bags (5), accessories (3). Total 79 items.
`/data/equipment.{locale}.json`	Locale-specific equipment data. Same locales as search-index above.

Agent discovery files

File	Description
`/llms.txt`	Compact LLM/agent manifest. Lists all JSON endpoints, key pages, score interpretations, languages and URL patterns. Start here for AI agent integration.
`/llms-full.txt`	Expanded agent context and important URL references for published pages.
`/urls.txt`	Complete sitemap-derived URL list. One absolute URL per line for all published pages.
`/robots.txt`	Standard crawl policy. All paths are allowed by default.

Markdown versions of review pages

Markdown versions of review and guide pages are available by appending index.md to any page URL. This provides clean, structured text for LLM context windows without HTML parsing.

Pattern: https://padel.how/{page-path}/index.md

Examples:

/equipment/racket/nox-at10-18k-2026-review/index.md
/equipment/shoes/babolat-premura-3-review/index.md
/equipment/overgrip/head-xtremesoft-overgrip-review/index.md

Score schemas

Racket score interpretation

Score range	Meaning
80+	Exceptional — minimal compromises
75–79	High-level — clear strengths, manageable trade-offs
70–74	Solid — noticeable limitations
65–69	Narrow-use or entry-level
Below 65	Strong compromises

Shoe score interpretation

Each of the 7 shoe categories is scored 0–10. Scores above 8.0 indicate a genuine strength in that attribute. The aggregate score reflects the rounded average across the evaluated criteria. A score of 55+ indicates a shoe suitable for regular competitive padel.

Overgrip score interpretation

Each of the 6 overgrip categories is scored 0–10 based on measured data (weight, length, moisture absorption) and on-court testing. A score above 8.0 in moisture_absorption indicates strong performance for sweaty-hands use.

Usage notes

All JSON is UTF-8 encoded with Content-Type: application/json.
Aggregate JSON files are regenerated when new reviews are published. Check the generated field where present to detect staleness.
The slug field in every item matches the directory name in the corresponding HTML URL, making cross-referencing straightforward.
Localized pages follow the pattern https://padel.how/{locale}/{path}/ where locale is one of: fr, de, it, es, pt, se, no, dk. English is the default at the root path.
For structured comparison of rackets, see the compare tool at padel.how/equipment/racket/compare/.

Quick start for agents

Fetch /llms.txt for the site summary and all endpoint patterns.
Fetch /rackets.json to get the full racket catalog with scores.
Fetch /rackets/{slug}.json for detailed FAQ and verdict text on a specific racket.
Fetch /shoes.json for the shoe catalog or /overgrips.json for overgrip data.
Use /data/search-index.{locale}.json for lightweight keyword lookup across the full site.