/basketball/tournament/{id}/events

Go APIloading...

GET

/api/basketball/tournament/{id}/events

Send

Path

The next fifteen scheduled fixtures in a tournament.

The fifteen are taken before the incomplete rows are dropped, not after. The original limits in SQL and then filters out any fixture whose home or away team failed to join, so a request can legitimately return fewer than fifteen; moving the filter into the WHERE clause would top the list back up and change what the client receives. The subquery preserves that order of operations.

The status check is a one-armed or(eq(status, "notstarted")) in the original — an or with a single branch, which is just the equality.

Path Parameters

Response Body

curl -X GET "https://example.com/api/basketball/tournament/0/events"

{  "data": [    "string"  ]}