DCO REST API - Search result too "small"

[DCIM_Support]

This question was originally posted on DCIM Support by corneliussen on 2017-09-22

---

Hi

Im investigating the REST API (v8.0) and have a problem with the "asset search" operation

https://(some-ip)/api/current/assets/search?q=blade

It is NOT returning all expected results. Is there a limit on the JSON data returned? The JSON result is always around approx max 1150 lines. And that is too few lines/results. I know there is more 😀

How do I overcome this? Also - i don't seem to be able to finde any documentation on any eventual pagination. Where can I find more info.

Best regards
Søren

(CID:125211050)

[DCIM_Support]

This answer was originally posted on DCIM Support by Christopherus Laurentius on 2017-09-25

---

Hi,

Taking the answer from similar question:

Just a note on the GET /assets/search operation: for performance reasons there is a limit to how many elements will be returned. It is capped at 50 items.That is a hardcoded limit that cannot be manipulated at runtime.

Regards,

Chris

(CID:125211453)

[DCIM_Support]

This comment was originally posted on DCIM Support by jda4u on 2018-02-23

---

Please allow the limit to be customized beyond 50.

(CID:128760604)

[DCIM_Support]

This comment was originally posted on DCIM Support by jda4u on 2018-02-23

---

Datacenters have more than 50 items in them...

(CID:128760607)

[DCIM_Support]

This comment was originally posted on DCIM Support by David Romero on 2017-10-09

---

We began using ETL instead. Schneider Electric took a good step towards REST, but crippled API to the point that its not ideal to script off of. The old SOAP API was better in my opinion.

(CID:126160751)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.