Event API result is a list of all updated files in an "entire" site.
For enterprise use-cases, the volume of this returned data is inevitably very large.
Thus, even if a part of site needs to be monitored, the network bandwidth is consumed unnecessarily and it casues the performance issue.
Could you add a filter function to Event API so that the API returns only events related to the files in the specified path collection?
 
This is the API asking to enhance
https://developer.box.com/en/guides/events/for-enterprise/

Event API does not include the path collection for updated files. Thus, to get the updated files, another File Info API should be called.
This situation increases the number of API calls and causes the complexity of the client program and the performance issue.
Could you include the path collection in Event API results?

Requests to extend maximum single file upload size beyond 32GB. Please comment with use cases and file size limit of request.

Box currently does not have the ability to show deleted files in a particular folder. Only the owner and the user who deleted files will see them in Trash but not by folder. With large numbers of files in multiple folders, this becomes quite unmanageable quickly and relying on the folder owner to restore files is unnecessarily restrictive.

Folders should have an option to see deleted files and if permitted (editor or higher, or a separate permission) allow users other than the owner and the user who deleted files to restore them.

Content sprawl is our #1 challenge. Please let us organize our folders. We don't want to interfere with the permissions, but I want to have an "Active Projects" folder and a "Project Archive" folder where I can drag and drop those relevant folders in.

Currently you can trigger on the metadata values for a file. Can we add the same trigger for a metadata change on a folder?

Situation: Parent folder metadata change should cause an action that affects all children. i.e. move the folder and all children to another location.

We want all files "locked" when opened so that any other user would be notified that the file is opened by another user and they can look in "read-only" view.

Allow forward slashes in Box Folder names

The current upload limit for the email listener in Box is 50MB. There should be options to increase.

We would like to have the ability to create two folders in different places within our BOX environment and for these two folder to stay sync'd. If we add a file into one folder it is added to the other folder also. If we remove a file from one of the folders it is removed from the other folder. What ever change takes place in one folder is duplicated in it's sync'd folder

The ability to have data residency for China to meet "The Cyber Security Law of the People's Republic of China"

Currently 32GB is available as part of the Digital Business Suite. Capturing requests to have a separate pricing or SKU for it outside of DB. Please note down your request / customer

Add more plan options for individuals. 100GB is not enough to store hardly any of my data.

Snowball(AWS) type of migration should be supported by Box. Especially the customers who have tons of files/folders as TB/PB level has a hard time for content to move from Windows servers to Cloud systems like Box.

I can create a bookmark to another folder in box, but the experience and visualisation of these is not useful - links to folders get lost in the file list.

Bookmarks to other folders in box, should be listed as a folder, not a file, perhaps with a different icon to show they are linked folders rather than hierarchic folders.

I think it's kind of a bug or i don't know: when the file i try to upload have in it's name "not so ordinary" characters i will get an error. Letters like these ones, with symbols: ä, á, ç, é, ñ, etc, there are others, you get the point. Just sayin`...

We need the ability when viewing a users list of files and folders to show only content owned by user. Right now files that have any collaboration at all do not show differently if owned by user or not. Ideally, we could toggle a view filter to show only files/folders owned by user if needed.