Mitie use Box platform to surface payslips to their employees. For this they use a Box UI element. As they analyse their API consumption they feel that the UI elements are using a lot of API calls - more than planned for and they are worried this will impact the price of their engagement come renewal. One thing in particular they have noticed is that when a user previews a document, the UI elements pre-fetches what looks like the next five documents, presumably for performance reasons. Since their users only every preview one document (the current months payslip) they are asking for the ability to turn off the prefetch as a configuration when the UI element is loaded on the page.

We have an open risk item on the Box platform due to lack of controls on change management.
Specifically:
Box console settings must be manually performed across dev, test and production environments.
Lack of automated mechanisms to maintain consistency with the settings across the environments may allow weaknesses in lower environments (dev/test) to be exploited to exfiltrate data or modify data or inconsistencies between functionality tested in lower environments and what is configured in prod.
We would like the ability to be able to configure the settings via API so we can build environment management into out CICD pipeline. We believe many other customers with tight security and compliance controls would be keen for the same.

It would be great if we have a bulk API option. I would like to pass in the list of entity ids(could be files, folders users etc) and get back the results. This will reduce the number of api calls we do to get all the information.

We try to manage client's storage accounts and the main problem is with rate limiting for a large clients.

Implementation can vary, either limit the response size or provide an ack id and developers can poll for the id and get the data back once the api is ready to spit out the data in form of CSV. This would greatly help us reduce the api calls

Before deleting a user from box system we can transfer the root folder from one user account to
another.
Once the root folder is transferred only then delete API must be triggered.
So in all, the delete operation will have to call two API one to transfer and another to delete.

But as the transfer API call will return synchronously.
For users with a large number of files and folders, this means the call could take minutes or hours to return.

So the delete operation will be in pending state until we receive the transfer API response.

Does box now have single API call to delete box user and also transfer the folder?

Lets consider the use-case below;
1. We are deleting box user - User1.
2. We have to trigger API call to transfer files for User1.
3. If the size of the files is too big we have to wait until the files are transferred or root folder gets empty for that user.
4. We have to wait till the time all files gets transferred or root folder gets empty.
5. Trigger API call to delete user once root folder is empty.

Here we have to wait till the root folder gets empty which might hamper the performance if the file size is large.