Skip to content
datasportsAPI

Referees & managersManager fixtures

Documentation

/

Type to filter the docs by title or path.

Referees & managersEndpoint 103 of 116

Manager fixtures

GET

/v2/managers/{id}/fixtures

Plan
All plans
Auth
Bearer dsa_live_…
Parameters
1 required · 2 optional
Returns
Fixture[]
Try in Playground

One page of the matches a manager has recently had or has coming up, divided 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. A manager who exists but has no matches to show gets 200 with an empty array.

01Parameters

  • idpathRequired

    DataSportsAPI manager id, a positive integer

  • typequeryOptional

    recent \| upcoming; upcoming when omitted

  • pagequeryOptional

    zero-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/managers/{id}/fixtures"

03Response

The top-level keys of the JSON body. Each object links to its full shape in the data reference.

data
Fixture[]
meta
type, page, count, hasNextPage; historyFrom is added if your plan excluded older fixtures
ObjectsFixture
Example response
{ "data": [ { "id": 203877, "status": { "type": "notstarted", … }, "startTime": "2026-10-25T20:00:00.000Z", … }, … ],
  "meta": { "type": "upcoming", "page": 0, "count": 5, "hasNextPage": false } }

04Errors

  • 400bad_request

    type is neither recent nor upcoming, or page is not a whole number between 0 and 50

Any key can also meet401unauthorized429rate_limited429quota_exceeded500internal_errorEvery error code