Get record positions by their time

Headers:

• Authorization: nadeo_v1 t={token} An access token for the NadeoLiveServices audience

Query parameters:

• {mapUid} string The UID of the map *
  Maximum: 50 map UIDs
• {score} integer The score/time (in milliseconds) to get the position for *

Body parameters:

• {maps} object[] The list of maps (needs to match query parameters) *
  • {mapUid} string The UID of the map *
  • {groupUid} string The ID of the group/season for a specific map *

The request body contains an array of maps, each identified by its mapUid:

{
  "maps": [
    {
      "mapUid": mapUid,
      "groupUid": groupUid
    }
  ]
}

Remarks:

• The groupUid "Personal_Best" can be used to get the global leaderboard.
• When using a different groupUid, make sure you’re only referencing currently open leaderboards. Maps with closed leaderboards will not be included in the response.
• The mapUid parameters in the URL has to correspond with a map in the request body.
• This endpoint supports up to 50 maps at once - they need to be added to the request body’s array as well as to the query parameters (see example below).
• This endpoint can sometimes be very delayed - there have been cases where it has returned data that was outdated for multiple hours. On average, this route should be up to date within about three hours - some maps are prioritized though (official campaign maps and current TOTDs), so they are typically updated every five minutes.
• If the authenticated account has a record on the requested map, no scores worse than that record can be requested - it’s recommended to use this endpoint with an account that does not have any records.
• scores must be greater than or equal to 1, otherwise the result for that mapUid will be omitted.
• Duplicate mapUids in the same group are not supported. The response will include the same position for all scores requested.
• The positions returned by this endpoint don’t correspond to existing records, instead they tell you what a new record’s position would be given the requested score.
• This is technically the same endpoint as get player records, but works differently if given query parameters.
• This endpoint may sometimes return an empty list ([]) even when passed valid parameters. It is not known why but it seems to be inconsistent. If you experience this issue, try to use different accounts and switch between dedicated/service accounts (see Auth for more information).

Example request:

POST https://live-services.trackmania.nadeo.live/api/token/leaderboard/group/map?scores[gjt2DWATrQ_NdrbrXG0G9oDpTfh]=15800&scores[XiGZvMOqIgT3_g0TdeFa0lxMp46]=17500

{
    "maps": [
        {
            "mapUid": "gjt2DWATrQ_NdrbrXG0G9oDpTfh",
            "groupUid": "Personal_Best"
        },
        {
            "mapUid": "XiGZvMOqIgT3_g0TdeFa0lxMp46",
            "groupUid": "Personal_Best"
        }
    ]
}

Example response:

[
    {
        "groupUid": "Personal_Best",
        "mapUid": "gjt2DWATrQ_NdrbrXG0G9oDpTfh",
        "score": 15800,
        "zones": [
            {
                "zoneId": "301e1b69-7e13-11e8-8060-e284abfd2bc4",
                "zoneName": "World",
                "ranking": {
                    "position": 294,
                    "length": 0
                }
            }
        ]
    },
    {
        "groupUid": "Personal_Best",
        "mapUid": "XiGZvMOqIgT3_g0TdeFa0lxMp46",
        "score": 17500,
        "zones": [
            {
                "zoneId": "301e1b69-7e13-11e8-8060-e284abfd2bc4",
                "zoneName": "World",
                "ranking": {
                    "position": 42,
                    "length": 0
                }
            }
        ]
    }
]

If a groupUid or a mapUid is invalid (or the referenced leaderboard is closed), the response will simply omit that map’s record.

If the query parameters reference a map that is not contained in the request body, the endpoint may return a 500 error.