This is an archive version of the document. To get the most up-to-date information, see the current version.

Pagination

By default, each page contains 30 records returned by the endpont to which you send requests.

To change this, you can use the following attributes:

  • Offset

This attribute helps you exclude the first N items from the response page.

  • Limit

This attribute helps you limit the maximum number of items that the server must return per page.

Pagination Note:

Veeam Backup for Microsoft Azure RESTful API returns resources in the default order based on its own semantics.

For example, to get a page with only 3 session records starting from the 20th page, you can use the following request.

GET https://<hostname>/api/v1/jobSessions?offset=19&limit=3

If it is possible to navigate to other pages, the server will also return the links to the first, previous and next pages.

"_links":    {

     "self": {"href": "https://abc.ukwest.cloudapp.azure.com/api/v1/jobSessions?offset=19&limit=3&display=Full"},

     "prev": {"href": "https://abc.ukwest.cloudapp.azure.com/api/v1/jobSessions?offset=16&limit=3&display=Full"},

     "first": {"href": "https://abc.ukwest.cloudapp.azure.com/api/v1/jobSessions?offset=0&limit=3&display=Full"},

     "next": {"href": "https://abc.ukwest.cloudapp.azure.com/api/v1/jobSessions?offset=22&limit=3&display=Full"}

}

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.