If your RMS account contains a large number of assets or jobs, the behavior of List operations depends on which api-version you use. Your existing code continues to work regardless of which version you are on - but if you are listing thousands of records, api-version=2026-04-14 gives you a more reliable and predictable way to page through results.

In this article:

How List results work

api-version 2026-04-14 and later

Earlier API versions

Fetching the next page

Example

If you are using the Azure SDK

Do you need a new api version?

How List results work

api-version 2026-04-14

List operations for entities such as assets or jobs return up to 1000 records per response. If the result set is larger, the response includes an @odata.nextLink field containing a URL to the next page. You follow that link to retrieve the next batch, repeating until no @odata.nextLink is present.

{
  "value": [ ... ],
  "@odata.nextLink": "https://{{api-endpoint}}/...assets?api-version=2026-04-14&$skiptoken=..."
}

This behavior applies whether or not you use the $top parameter.

Earlier API versions

List requests return all matching records in a single response with no page limit. While this is acceptable for accounts with a small number of entities, for large datasets, it can result in slow response times or timeouts.

To scope results and enable pagination, use the $top parameter. When $top is set and more records exist beyond the requested page, the response includes @odata.nextLink - follow that link to retrieve the next page.

Earlier API versions will continue to work in the same way. You don't need to change any of your existing requests.

RMS was built as a replacement for Azure Media Services (AMS) and initially shipped with a single API version matching the AMS API surface. Because the behavior was identical across all requests, there was no versioning to validate separately - existing AMS-compatible integrations worked with RMS without changes. api-version=2026-04-14 is the first version to introduce new behavior beyond that baseline. This makes it the only api version that changes the API behavior.

Fetching the next page

When the response contains @odata.nextLink, use that URL directly as the next request - no modification needed. The link includes all necessary parameters to retrieve the next page.

Repeat until the response no longer contains @odata.nextLink, which indicates you have retrieved the last page.

Example

First request:

GET https://{{api-endpoint}}/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}
    /providers/Microsoft.Media/mediaServices/{accountName}/assets
    ?api-version=2026-04-14

Response (partial - more results exist):

{
  "value": [ ... ],
  "@odata.nextLink": "https://{{api-endpoint}}/.../assets?api-version=2026-04-14&$skiptoken=abc123"
}

Next request - use the link as-is:

GET https://{{api-endpoint}}/.../assets?api-version=2026-04-14&$skiptoken=abc123

Continue until a response arrives with no @odata.nextLink - that is the final page.

If you are using the Azure SDK

RMS mirrors the AMS API surface, which means it is compatible with the Azure SDK for .NET, Python, JavaScript, and Java - the libraries originally built for AMS by Microsoft that are now open-source and maintained independently.

If you are using one of these SDKs, you do not need to handle @odata.nextLink manually. The SDK parses pagination links internally and fetches subsequent pages on its own.

To use api-version=2026-04-14 behavior, update the API version value in your SDK configuration.

Do you need a new api version?

If your account has a small number of assets, jobs, or streaming locators, there is no urgency - earlier API versions handle these result sets without issue.

Consider upgrading to api-version=2026-04-14 if:

• You are listing entities without $top and experiencing slow responses or timeouts.
• You want consistent pagination behavior without managing $top manually.
• Your entity count (e.g., jobs) is growing, and you want to avoid issues before they arise.

See more:

• RMS filtering, ordering, and paging
• Asset - List
• Job - List
• Streaming locator - List