topic Re: maxRecords query parameter over 500 in Software Development Kit (SDK) and API Discussions

maxRecords query parameter over 500

CSiegle — Wed, 04 Jun 2025 15:35:35 GMT

Group -

OCAPI 1.2

I'm trying to retrieve greater than 500 records from the GET volumes REST call. If I set the maxRecords query parameter to a number greater than 500, I always get 500 records. However, the query will be adjusted downwards if I place a number less than 500.

REST syntax:

https://apiserver:8443/api/1.0/ontap/volumes?maxRecords=10000

Is this a bug or am I missing something?

Re: maxRecords query parameter over 500

ekashpureff — Sat, 07 Jan 2017 07:22:52 GMT

CSiegle -

Yes, you're missing something.

There was a race condition bug with the old 7-mode API calls to get various objects, including volumes.

Hence the max records for the new APIs.

BCP is to get 20 records at a time (default) and populate the 'next' tag with the results from the previous call.

I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, Fast Lane US http://www.fastlaneus.com/
(P.S. I appreciate 'kudos' on any helpful posts.)

Re: maxRecords query parameter over 500

pukale — Sat, 07 Jan 2017 19:08:58 GMT

This is as per design. at the most, you can fetch 500 records. this is done considaring many factors. one of them is performance. still, if you wanted to have maxrecords more than 500, please get touch with product management.

Re: maxRecords query parameter over 500

pukale — Sun, 08 Jan 2017 06:23:25 GMT

If your requirement is get records beyond 500, then please use nextTag. This, you will find end of each response body

Example:

https://apiserver:8443/api/1.0/ontap/volumes?NextTag=<nextTagValue>

Re: maxRecords query parameter over 500

CSiegle — Mon, 09 Jan 2017 00:31:58 GMT

Great! nextTag worked well. Thanks.

Re: maxRecords query parameter over 500

RameshN — Sat, 21 Jul 2018 15:38:44 GMT

curl -v -k -u admin:$Pass -L -H "Content-Type: application/json" https://10.64.56.251:8443/api/5.0/ontap/aggregates?maxRecords=3

Got the nexttag value like this "nextTag":"PiM+bG9jYWxob3N0OnR5cGU9b2N1bSx1dWlkPWxvY2FsaG9zdH4zLypAbWF4UmVjb3Jkcz0zPCM8"

and

curl -k -u admin:$Pass -L -H "Content-Type: application/json" https://10.64.56.251:8443/api/5.0/ontap/aggregates?nextTag=PiM+bG9jYWxob3N0OnR5cGU9b2N1bSx1dWlkPWxvY2FsaG9zdH4zLypAbWF4UmVjb3Jkcz0zPCM8
{"status":{"code":"FAILED","error":{"errno":2004,"message":"The specified parameter values are invalid.","reason":" Invalid parameter value for nextTag "}}}

Please help

we have more than 500 volumes; for the nexttag I am testing with aggregates.

thanks
Ramesh