.png%3Falt%3Dmedia%26token%3D21947f78-6585-4468-bf7f-df26530c8a43)
.png%3Falt%3Dmedia%26token%3D21947f78-6585-4468-bf7f-df26530c8a43)
Ordering
For paginated endpoints, the API supports ordering on a specific field. Read more on how to use ordering on this page.
The
order query parameter is used to specify the order in which paginated results should be returned. By default, results are returned in ascending order. However, you can use the order parameter to specify that results should be returned in descending order instead.Using ordering allows for more convenient results to be returned, next to that it can potentially save you from making API calls as you don't have to propagate through redundant results.
Parameters
Parameter | Required | Description |
|---|---|---|
order | No | The order in which results should be returned ( asc or desc). |
Usage
To use the
order query parameter, simply include it in the request URL for paginated endpoints. For example:https://api.sportmonks.com/v3/football/fixtures?api_token=YOUR_TOKEN&page=2&order=desc
In this example, the API will return page 2 of results for the
leagues endpoint, in descending order.The field used for ordering differs per endpoint, you should consult the endpoints documentation page to see what field the ordering applies on.
Last modified 1mo ago