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.
243 results found
-
Could add "item_execute_integration" to scopes page.
could add "itemexecuteintegration" to https://developer.box.com/docs/scopes#section-application-scopes ?
I think the developer gets angry or confuse.
1 vote -
Make license type info available via API
We'd like to get the license type info (free or paid) when getting the below log by API.
- eventtype:COLLABORATIONINVITE
- event_type:SHARE
Account Type: Unmanaged User / Managed User, etc
User TypeL Lite (10GB) / Enterprise (Yearly), etc3 votesThis is not currently planned as there is unclear purpose and implementing it may expose sensitive information.
-
Add Custom URL for shared link via API
Please add support to set custom url when setting up a shared link via API.
We would like to have this feature to automate our operation when new contents have been added to Box.
2 votes -
copy move or rename API events to include id of both the target and origin locations
In copy/move/rename events, the API should include the id of both the target and origin locations (from-to)
4 votes -
Add field to see how a collaborator was added to a folder
Currently the has_collaborations field with the API will show if a user was added as a result of inheritance (waterfall permissions) or if they were added directly to the specific folder, but there is no way to distinguish between those. For performance reasons and limit the amount of calls, it would be helpful if there was a filed that could be added to distinguish how a collab to a folder occurred
2 votes -
Populate accessible_by field in get collaborations
When managing collaborators, the end user needs to see who they have sent invitations to, even if those invitations have not yet been accepted and the other user has not created a box account. The call to get collaborations on a file or folder returns accessible_by: null for pending collaboration requests, essentially hiding the details of the pending requests and making it impossible to display those details to a user in a custom app. This data is definitely available because this feature exists in the main Box.com interface, but has not been exposed to the APIs yet.
4 votes -
Allow Search API call to search using wildcards
if I wanted to get the item ids of all files within a users account, I would have to run the Get Folder Items for all subfolders. If there’s a large folder tree, it would either take to long to iterate through all subfolders or I would run into an API rate limitation. It would be easiest if the Search API call can allow searching using wildcards so it would just take one API call to get a list of all item ids.
5 votes -
Get list of service accounts via API
Right now the only way to get a list of automation users (service accounts) is via the web UI. The application does not have UI access, and since the users can be provisioned and deleted frequently, we do not want to rely on the manual work.
13 votes -
Update Classifications via Box's CLI
Update existing Classifications on files via Box's CLI
2 votes -
Add length of field to API documentation
It would be nice to explicitly mention the length of some of the fields. In our enterprise account all the users had 10-digit UIDs, so I thought that was the standard length, but we had some users with preexisting lite accounts rolled in and a few of them had 8-digit or 9-digit UIDs. I see now that the example UID provided had 9 digits, so my bad there, but I initially just looked at the 'id' attribute under 'user object' to try and find the length and it would be nice I think to have something like 'id / string…
1 voteThanks for the suggestion. We generally don’t provide lengths for fields unless there is a concious decision to define a specific length or range as a contract. Given that the type of field for user id is a string, the fact that user id values ranged from 8-10 digits is an implementation detail, not a guarantee.
-
Make source.parent.name to include all of path
source.parent.name show just folder name.
For example, if the collaborator folder is A and it lcates “All files/A”. the customer get api.box.com/2.0/events?streamtype=adminlo..,
source/parent/name just show A. This behavior make the user not to find the folder easily.
It should be shown “All files/A”2 votes -
New event type for modification of upload-email properties
A new event type for modification of upload-email properties, such as access type (in addition to the existing enable/disable events for upload email functionality)
1 vote -
Improve CORS whitelist wildcard support
I would love to be able to use wildcards in CORS with a little more specificity. In particular, for review apps on Heroku, you will have a url that is auto-generated for each pull request, so something like http://my-app-dev-pr-523.herokuapp.com. I would like to be able to add http://my-app-dev-pr*.herokuapp.com to the CORS list but it currently flags that is an improper URL so I have to do the much more broad (less secure) http://*.herokuapp.com
1 voteThis is not currently planned
-
Folder upload endpoint for API
The ability to copy a folder from a local machine and upload it via the API
1 vote -
Rollback option when db crash
After creating folder or uploading files into box there will be chance of occuring backend database crash or lose connection between datasource . In this case we should roll back our transaction(like revert folder creation or file upload).
1 voteMany actions in both are idemptotent and can be safely retried. For those which are not, it is the responsibility of a client to implement transaction guarantees if required. There are common patterns for this such as the two-phase commit and SAGA pattern. If there is more information for a specific capability that is required to faciliate these, please add that to the comments.
-
Expose ability to restore versions of files via API
It would be beneficial to expose this information via API when interacting with file versions to enable this for App Users via a portal
1 vote -
Ability to add a message when we invite collaborators via Create Collaboration API
This can be done on webapp (message field). We want to do this through API
6 votes -
Pull list of all collaborators with a certain user_type at a folder level
Currently, you can only search by user_type at the enterprise level as documented here: https://developer.box.com/v2.0/reference#get-all-users-in-an-enterprise
It would be helpful to be able to do this at a folder level as well.
2 votes -
Surface either EID or user_type when requesting collaboration object
Currently, requesting a collaborationobject does not surface either EID or usertype. (as seen in https://developer.box.com/v2.0/reference#get-collabs)
2 votesThis request is not currently on our roadmap but we’ll update this request if that changes. In the mean time, you can use a subsequent request to get the user information and specify the enterprise in the `fields` query string parameter.
-
1 vote
- Don't see your idea?