/tournament/upcoming-fixtures-multi

Go APIloading...

POST

/api/tournament/upcoming-fixtures-multi

Send

Body

The next fixtures across several competitions at once.

uniqueTournamentIds wins when both are supplied. A cup is one unique tournament split across a tournament per group, so filtering by tournament id alone drops most of its fixtures; tournamentIds stays supported for callers that already send it.

The failure branch answers with a message and no error key, unlike most of the API. That is the original's shape.

Response Body

curl -X POST "https://example.com/api/tournament/upcoming-fixtures-multi" \  -H "Content-Type: application/json" \  -d '{    "days": 0,    "tournamentIds": [      0    ],    "uniqueTournamentIds": [      0    ]  }'

{  "data": [    {      "awayTeamId": 0,      "awayTeamName": "string",      "homeTeamId": 0,      "homeTeamName": "string",      "id": 0,      "internalId": 0,      "slug": "string",      "startTime": 0,      "status": "string",      "tournamentId": 0,      "venueId": 0    }  ]}