API - Wrong scope ? getOrganizationDevicesMemoryByDevice

[Raphael_L]

Hi ,

To whom ever reads this ( hi Oren 😁 )

Is this expected that this call getOrganizationDevicesMemoryByDevice is named like a org-wide call but needs a specific networkId ?

Whenever I see a getOrganizationXYZ call , I never expect to specify a network.  

Summarizes memory status across devices of a given network . To me this feels more like getNetworkDevicesMemoryByDevice , no ?  🤔

[Philip D'Ath]

Isn't that an array of network IDs, like a filter? 

I think that should be made an optional parameter. 

[Raphael_L]

Exactly , I forgot to mention it but if you don't specify a network you will get a http 400 requiring a networkId ( at the moment )

[obrigg · Accepted solution]

Hi Raphael 😁

We started exposing API operations that were used by the UI and not the API as beta operations. You can expect to see more beta operations being added in the coming weeks/months.

This specific one will be deprecated in favor of a new operation the assurance team is working on. It makes little sense for an org-wide operation to have a Network ID as a requirement.

[Raphael_L]

Excellent news !  I will keep an eye out for these new calls 😉

As always , if you need some benchmark on a large org, let me know !