VenuesEndpoint 105 of 116
Venue fixtures
https://api.datasportsapi.com/
- Plan
- All plans
- Auth
Bearer dsa_live_…- Parameters
- 1 required · 3 optional
- Returns
Fixture[]
Returns one page of past or scheduled matches at a venue in a single sport, split by the same rule as team fixtures.
Worth knowing
upcoming covers matches yet to start, soonest first; recent covers live, finished and called-off matches, newest first. If the venue has no matches in that sport, the response is 200 with an empty array.
01Parameters
idpathRequiredDataSportsAPI venue id, a positive integer
sportqueryOptionalsport slug taken from VenueProfile.sports; when omitted, the sport played most often at the venue
typequeryOptionalrecent \| upcoming; upcoming when omitted
pagequeryOptionalzero-based page number, a whole number from 0 to 50 (defaults to 0)
02Request
The same call from the command line and each SDK. The SDK lines assume a client created with your key; left out, it is read from DATASPORTSAPI_API_KEY. Installing a client: SDKs & CLI.
curl -H "Authorization: Bearer dsa_live_…" \
"https://api.datasportsapi.com/v2/venues/{id}/fixtures"03Response
The top-level keys of the JSON body. Each object links to its full shape in the data reference.
dataFixture[]meta- sport, type, page, count, hasNextPage; historyFrom is added if your plan excluded older fixtures
{ "data": [ { "id": 701233, "status": { "type": "finished", … }, "home": { "name": "Arsenal", … }, "away": { "name": "Everton", … }, … }, … ],
"meta": { "sport": "football", "type": "recent", "page": 0, "count": 30, "hasNextPage": true } }04Errors
- 400
bad_requesttype is neither recent nor upcoming, page is not a whole number between 0 and 50, or sport is not recognised
unauthorized429rate_limited429quota_exceeded500internal_errorEvery error code