Help shape the future of Box
Welcome to Box Pulse, our product feedback tool powered by UserVoice. Got an idea for how to improve Box? Share it with us and gather support or vote on other people's ideas. Your feedback is essential to informing roadmap decisions and shaping the future of our products. Thanks for joining our community!
See user guide here.
231 results found
-
Make API rate limits more sophisticated, especially for large enterprises
When working with a Box Enterprise that has tens of thousands of users, scripts designed to do things like user information syncing, group syncing, or user provisioning/deprovisioning often run into real issues with the Box API rate limits.
Some calls (e.g. downloading or uploading a file) are clearly significantly more resource-intensive than others (e.g. getting a user’s aliases). The method Google has implemented for the Gmail API (see https://developers.google.com/gmail/api/v1/reference/quota) seems like a really great way to balance the need to protect the back-end systems against the need for increased performance for less-intensive calls. It would be nice if Box…
32 votesThis will be considered for the FY24 roadmap, not planned for FY23
-
Add Linux installer packages for Box CLI
Testing out the Box CLI and request official Linux support for Ubuntu or RHEL. Would like an easy install via apt-get or Yum.
99 votesWe do not plan to address Linux support for the Box CLI.
-
View and configure enterprise webhooks in the UI
Provide a UI where we can see the webhooks that have been created across our enterprise applications. We have had some webhooks deleted because of users deleting folders or webhooks. Also, we have a case where a webhook stopped triggering. After calling the 'list all webhooks' api, we don't see that webhook created. No one has deleted it so it's difficult to understand what happened to this webhook trigger.
3 votes -
1 vote
At this point we have no plans to create powershell specific SDK. However, the Box Command Line utility can be called from within powershell which may be of help. https://developer.box.com/guides/tooling/sdks/cli/
Furthermore there is some good (if a bit dated) information on how to use the Windows SDK from within Powershell here: https://community.box.com/t5/Platform-and-Development-Forum/Automating-box-processes-using-powershell-and-the-box-windows/m-p/50342
-
Expose user's last activity date and last login date via API
The Box CLI:GET commandlet is a good tool but if it could grab more basic information, it would be great.. For my company, we would like to see the Last Activity and Last Login of an end user's Box Account. This would help us determine when to de-provision a Box Account after we can verify it hasn't been used in X amount of time.
5 votes -
A way to be able to select the rights of the developer console, which is similar to allow users to use Box Relay.
A way to be able to select the rights of the developer console, which is similar to allow users to use Box Relay.
This is a way to prevent users not to make sand boxes and API.7 votes -
Read Enterprise Settings using API
Is there a way to read Enterprise Settings using API? That would be much beneficial where the Admin can choose certain settings like Storage and there wont be a necessity to change the Code every time the Admin wants to change the settings. The API can read the existing settings and manage users based on those configurations. Currently, the application that manages Box accounts has to store those locally and every time there is a change in those settings, that calls for a Change management and code deployment.
3 votes -
File-level Collaboration Webhook
I'd like to create a file-level webhook so that I can take action when a file's collaboration(s) have changed, but unfortunately there is currently no webhook trigger for collaborations on a file. Please add support for COLLABORATION.* webhook triggers on file objects.
12 votesThanks for the suggestion! We don’t currently plan to add a Webhook event for file-level collaboration events, but if anything changes we will update this suggestion. If you have specific use cases to share, please add them as comments to this suggestion.
-
Allow http://127.0.0.1 as redirect_url in published box apps
It is currently disallowed to use redirect_urls of the form http://127.0.0.1 in published apps.
These give the error "insecureredirecturi".
These are allowed in unpublished apps.
Having a redirect to 127.0.0.1 is very useful for native apps which run on the users computer (eg rclone https://rclone.org ).
It is pretty much impossible to do https to 127.0.0.1 - you can't get a valid certificate for it. See this link for details: https://letsencrypt.org/docs/certificates-for-localhost/ - and also for reasons why using http://127.0.0.1 is treated as secure by browsers.
I'll describe how rclone, a native CLI app works. Rclone runs on the…
1 vote -
Ability to ban App Token Applications
Currently, we can require users to get approval from admin to authorize apps, but that leads to a number of emails generated to the admin. We want the ability to ban users from creating App Token Applications.
3 votes -
macOS SDK support
It would be great to see full macOS support in the Box SDK.
I realize that the name of the Apple-flavored SDK is "box-ios-sdk", but "osx" is listed as one of the supported platforms. It compiles and links just fine, but the code path bails on OAuth sign in support.
It looks like most of the SDK would work fine for API calls post authentication, so I think it's mainly a matter of wiring up browser-based sign-in like Dropbox does for their SDK: https://github.com/dropbox/SwiftyDropbox. This seems to be confirmed by a response from @sujaygarlanka in a submitted GitHub issue: …
1 vote -
API-level access to Box Admin Console settings
Amazon has many EIDs and their security team needs to be able to apply and monitor enterprise settings in a centralized, scalable way.
1 vote -
Box CLI - need more output options for folders:items.
Specific to "box folders:items" but probably other commands as well:
1) If I'm asking for --csv, AND specifying the fields via --fields=, I don't need a header telling me the fields I just requested. I'd like an option to disable the header, or default disable it and make me add it back.
2) If I'm asking for specific fields as --csv, give me just those fields. If I'm asking for --fields=id I don't want it served back to me as "folder,#", I don't want to know it's a folder. If I later do something against that ID that is not…
3 votesHello,
We are not planning on changing --csv or --json behaviour in CLI.
Fields ID and Type are returned by API by default and removing them from the CLI would mean to modify the existing CLI behaviour.
-
Add "synchronize" or "versions" to the BoxCLI "folders:upload" functions
I am looking for a way to "synchronize" a folder and all of it's contents with the BoxCLI.
So, lets say i run this command:"box folders:upload /root/test_folder --parent-folder=%ID%"
How can i upload the folder, and only "Update" what has changed?
It would be nice to have something for "Folders" like you have for "Files"
"box files:versions:upload FILEID PATH"
maybe - "box folders:versions:upload FOLDERID PATH"
which would update all of the contents of the folder, version stuff that exist, add items that don't.
I know i can "box:folders:delete"... then "box:folders:upload" again.. but seems a waist of bandwidth and time..
3 votes -
Add "Box DICOM Import" functions to the BoxCLI
One thing that would be handy is to be able to upload a folder (of dicom files) and process the contents with the "Box DICOM Import" functionality using the BoxCLI.
Maybe something like: (add a flag to current box:folders:upload command)
"box folders:upload /root/test_folder --parent-folder=%ID% --dicom-import"
That would be Nice!
3 votes -
Provide read-only scope for user information
I'd like to provide our central identity management team a way to tell whether or not a given Box user has a > 0 byte usage before they delete the user's account (for example, as someone leaves our organization). I'd like to give them read-only API access to https://api.box.com/2.0/users, without giving them any additional access. Support tells me that this isn't currently possible. It'd be nice if it was--this could be useful for a number of other uses, too, such as reporting.
2 votesThanks for the suggestion! Providing a read-only scope for Users via API is not currently on the roadmap, but we’ll update this request if that changes.
-
Add Support for Reading Tags on Weblinks
You can currently add tags for weblinks via the API, but can't read them. This is a huge oversight, which makes it nearly impossible to add any sort of dynamic filtering capabilities. That is, there's no way to return (or parse) out a list of available tags -- since you can't read any of them.
To accomplish any sort of dynamic filtering, you have to bypass the tags altogether and add them to a field you can read. For example, after a colon in the title field. However, that's a temporary stop-gate solution with issues of its own.
2 votes -
Provide a Go / Golang SDK for Box
Add Golang SDK
1 voteAt this point we have no plans to add SDK support for Go/Golang
-
Custom notifications using Box API
Using Box API there is no way to create custom user notifications. It might be helpful to send some information to the customer that some documents have been moved, imported, etc. A user can monitor the folder but this would be a valuable extension for the API for platform developers.
12 votesThanks, this is a great suggestion but not one that is currently on our roadmap. In the mean time, you can consider using Webhooks to get relevant events and make use of a simple transactional email/sms API such as those provided by Twilio/Sendgrid or Amazon SES to send notifications based on those events.
-
Allow Enterprise Event API Endpoint to access 7yrs worth of data to match the activity reports provided by the web app
Enterprise Events API endpoint only allows retrieval of events up to one year back. Activity reports in Box go back 7 yrs. Events contain a lot more useful data than activity reports so the request is to match the retention period between the two so the same amount of data can be collected via the API or web application.
9 votesBox does not currently plan to extend the lookback period fo Enterprise Events.
- Don't see your idea?