> ## Documentation Index
> Fetch the complete documentation index at: https://padelapi.org/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# The FIP World Cup is coming

> The FIP World Cup is about to start and the Padel API is ready, with full support for team tournaments. Now is the time to update your app.

![Padel API FIP World Cup 2026](https://ik.imagekit.io/ferranfigueredo/tr:w-1920,h-1080/padelapi/padelapi-fip-world-cup-2026_yyY76i2pn.png)

**Hello developers,**

The **FIP World Cup** starts in Doha on **2 November**. Sixteen nations per category, six days, two titles. It is the best week of the year to have a padel app.

The Padel API is ready. Your app can be too, in one prompt. Paste this into your AI code agent:

```
Read https://padelapi.org/docs/guides/team-tournaments.md and update our Padel API integration to support team tournaments.
```

That is the whole update. If you prefer to see what changes, here are the three points.

## 1. How it is played

Teams, not pairs. They play a round robin in groups, then a knockout. Every tie between two teams is **three pair matches**, and the first team to win two takes it. If the first two decide it, the third is not played.

A new **format** field tells these tournaments apart: `pairs` on everything you read today, `teams` on these. One field, one branch. The rest of your calendar stays the same.

![Padel API Team Tournaments](https://ik.imagekit.io/ferranfigueredo/tr:w-1200/padelapi/padelapi-tournament-teams_Sztvjxw90.png)

## 2. Draws and ties

Each phase is a value of the `draw` filter you already use. `?draw=group` gives you the round robin. `?draw=main` gives you the knockout, quarterfinals to final. Add `?draw=placement` for the ties below the podium.

Every match in a team tournament brings a new `tie` object:

```json theme={null}
"tie": {
  "id": "men-group-0-7",
  "group": "A",
  "team_1": "Argentina",
  "team_2": "Spain",
  "rubber": 1,
  "score": { "team_1": 2, "team_2": 1 },
  "winner": "team_1"
}
```

The three matches of a tie share the same `id`. Group by it and you have the tie, with `rubber` giving the order. `score` and `winner` belong to the tie, not the match, so you never count rubbers yourself.

![Padel API Team Tournament Draws](https://ik.imagekit.io/ferranfigueredo/tr:w-1200/padelapi/padelapi-tournament-tiers_4pblDZC4r.png)

## 3. What changes

Three details to check before November:

* A match can come back as **`not_played`**: both pairs on the sheet, no result. Handle it next to `bye` and `walkover`.
* Winning the final match is not winning the title. A pair can lose its match and still be champion. Read `tie.winner`, not the match's `winner`.
* `winners` on the tournament holds the whole winning team: six players per category instead of two.

The [Team Tournaments guide](https://padelapi.org/docs/guides/team-tournaments.md) has the rest: the full field reference, a worked example that rebuilds a group table and the details that are easy to miss.

No need to wait until November. The 2024 edition is already in the API as [FIP World Padel Championships Qatar 2024](https://padelapi.org/explore/resources/tournaments/258), group stage and every knockout tie included.

Point your integration at it now and you will be ready before the first ball in Doha.

***

Thank you for being part of the Padel API community.

Your feedback drives what we build next. Feel free to share your thoughts or suggestions at [ferran@padelapi.org](mailto:ferran@padelapi.org).

Best regards,


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.