282 results found

1. Webhook V2 trigger filter

   It will be awesome if we can get some filtering option so that we can reduce calls to target API.
   In my use case, I need to process only images of specific file extension when uploaded and so it will be helpful to filter out other file extensions.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. API Request - API for Document preparation in an iFrame

   ability to expose document preparation in an Iframe through the API

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Box MCP Connector: Add Binary File Upload Support (.xlsx, .pptx, .docx)

   The Problem
   The Box MCP (Model Context Protocol) connector, used to integrate Box with AI platforms like Claude (Anthropic), currently supports only plain-text file uploads. The uploadfile and uploadfileversion tools accept text-only content and support a limited set of extensions: txt, md, csv, html, json, and a few others.
   Binary file formats — specifically .xlsx, .pptx, and .docx — cannot be uploaded through the MCP connector. The connector's own documentation references a getupload_url path for binary uploads, but that method is not exposed as a callable tool in the current implementation.

   Why This Matters
   AI-assisted workflows are increasingly the norm for SMB and enterprise teams. When an AI tool generates a finished Excel model, PowerPoint deck, or Word document, users expect it to land directly in Box, just as it would if they saved it manually. Instead, they're forced to download the file from the AI interface and drag it into Box Drive by hand. That's friction that breaks the workflow and defeats the purpose of the integration.
   For comparison, major document-sharing platforms work without problems.

   What We're Asking For
   Enable binary file upload support in the Box MCP connector for common formats, including .xlsx, .pptx, and .docx.

   Who This Affects
   Any team using Box alongside an AI platform (Claude, Copilot, custom GPTs, or any MCP-compatible tool) that generates Office-format files. This is a growing segment — and right now, Box is the bottleneck in every one of those workflows.
   Please upvote if your team runs into this. The fix is well-defined, and the precedent already exists in competing connectors.

   The Problem
   The Box MCP (Model Context Protocol) connector, used to integrate Box with AI platforms like Claude (Anthropic), currently supports only plain-text file uploads. The uploadfile and uploadfileversion tools accept text-only content and support a limited set of extensions: txt, md, csv, html, json, and a few others.
   Binary file formats — specifically .xlsx, .pptx, and .docx — cannot be uploaded through the MCP connector. The connector's own documentation references a getupload_url path for binary uploads, but that method is not exposed as a callable tool in the current implementation.

   Why This Matters
   AI-assisted workflows… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Add file and folder move operations to the Box integration for ChatGPT/OpenAI

   Subject: Add file and folder move operations to the Box integration for ChatGPT/OpenAI

   Hello Box Support,

   I am using the official Box integration within ChatGPT. The integration can currently list my files, create folders, upload files, rename items, and inspect permissions. However, it does not provide an action for moving an existing file or folder to another Box folder.

   For example, I asked ChatGPT to:

   1. Create a folder named !
   2. Move the files and folders in my Box root directory into that folder

   ChatGPT successfully created the folder, but it could not move the existing items because the Box integration did not expose a file or folder move operation.

   I confirmed that this is not an account-permission issue. I own the files, and my Box permissions allow deleting, downloading, renaming, uploading, and sharing them.

   Could you please clarify:

   1. Is the absence of file and folder move operations an intentional security restriction?
   2. Is this limitation controlled by Box, OpenAI, or the configuration of the Box connector/MCP integration?
   3. Could Box add supported actions for:

   • Moving a file to another folder
   • Moving a folder to another folder
   • Moving multiple selected items in one operation
     1. Could the integration use Box’s normal item-update API while respecting the user’s existing Box permissions and requesting confirmation before moving multiple items?

   This capability is important because without move operations, ChatGPT can inspect and create Box content but cannot perform basic file organization workflows.

   Please forward this as a feature request to the team responsible for the Box integration with OpenAI/ChatGPT.

   Thank you.

   Subject: Add file and folder move operations to the Box integration for ChatGPT/OpenAI

   Hello Box Support,

   I am using the official Box integration within ChatGPT. The integration can currently list my files, create folders, upload files, rename items, and inspect permissions. However, it does not provide an action for moving an existing file or folder to another Box folder.

   For example, I asked ChatGPT to:

   1. Create a folder named !
   2. Move the files and folders in my Box root directory into that folder

   ChatGPT successfully created the folder, but it could not move the existing items because the Box integration… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. API Endpoint to Manage Custom Apps

   There are not currently any API endpoints to call for custom apps - ideally there would be the ability to manage scopes, disable/deauthorzie + enable/authorize, delete apps (both server and user auth)

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Auto-Generated/System Generated Folder Creation via API

   Currently, if your enterprise settings have the 'Restrict Content Creation' setting as enabled, it also stops any root level folders appearing that are generated by Box, such as the "My Sign Requests folder"

   My understanding is that this folder's existence makes it so a user doesn't have to specify a folder for the sign request to go into. However, the lack of this folder existing makes it so that you do need to specify a folder for each request. We have many users who would prefer that all of their sign requests are present in the same folder, that leaves me with two current options:

   1) Make a new folder for everyone; as well as any future users who get provisioned
   2) Perform the following actions for everyone that we want the folder to exist for:

   a) Perform a managed log in for an affected user
   b) Start a Sign Request
   c) Back out of the request to generate the folder
   d) Log out of the managed log in instance

   Then after performing that for everyone, we would re-enable the 'Restrict Content Creation' setting again.

   It would have been ideal if we could use the API to generate any of these types of system-generated folders, such as My Sign Requests, My Box Notes, My Canvases, etc. even if the root level creation is restricted to admins.

   Currently, if your enterprise settings have the 'Restrict Content Creation' setting as enabled, it also stops any root level folders appearing that are generated by Box, such as the "My Sign Requests folder"

   My understanding is that this folder's existence makes it so a user doesn't have to specify a folder for the sign request to go into. However, the lack of this folder existing makes it so that you do need to specify a folder for each request. We have many users who would prefer that all of their sign requests are present in the same folder, that leaves… more

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Restrict CLI authentication to specific users

   In Box Clients, the only options for CLI authentication are to enable or disable it for all users. I would like to be able to enable it for specific users only.

   -in Japanese-
   Box Clientsで設定可能なCLI認証は全ユーザーに対して有効か無効しか選択ができません。特定のユーザーのみ有効化できるようにしてほしい

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Add PKCE Support for OAuth2 Applications

   Currently, Box requires developers to use a client secret for OAuth 2.0 apps, which in turn requires standing up and maintaining a backend service just to exchange authorization codes securely.

   While this is secure, it creates a huge amount of friction for developers who want to build modern, client-side applications such as single-page apps (SPAs) or mobile apps. In many cases, the only reason a backend exists is to hold a secret, nothing else.

   If Box supported PKCE (Proof Key for Code Exchange), developers could authenticate directly from the client without needing a backend at all, just as they can with platforms like Microsoft Entra, Google Identity, and Okta.

   This would dramatically reduce time to market, lower costs for developers, and make Box much easier to integrate into modern front-end-first workflows.

   Example Scenario

   A developer wants to build a React-based file manager using Box APIs.
   Under the current model, they must:

   1. Deploy a backend to safely store the client secret.
   2. Manage hosting, scaling, and security for that backend.
   3. Build and maintain the OAuth exchange logic.

   With PKCE, none of that is necessary. The developer could securely authenticate directly from the browser, accelerating development and reducing costs.

   Currently, Box requires developers to use a client secret for OAuth 2.0 apps, which in turn requires standing up and maintaining a backend service just to exchange authorization codes securely.

   While this is secure, it creates a huge amount of friction for developers who want to build modern, client-side applications such as single-page apps (SPAs) or mobile apps. In many cases, the only reason a backend exists is to hold a secret, nothing else.

   If Box supported PKCE (Proof Key for Code Exchange), developers could authenticate directly from the client without needing a backend at all, just as they can… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. The maximum number of Platform apps that can be registered should be increased.

   Currently, the maximum number of approved Platform apps is limited to 100.
   If we create an app for each affiliated company within the tenant, 100 is not sufficient.
   We would like the maximum number of Platform apps that can be registered to be significantly increased.

   (In Japanese)
   現在、アプリの登録上限は100件までですが、テナント配下で組織ごとにアプリを作った場合、足りなくなる可能性があります。
   登録できるPlatformアプリの数をもっと増やしてほしい

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Ability to Toggle AI Autofill on Folders via API

    AI Autofill can only be enabled on folders through the Box UI. Having an API endpoint to enable AI Autofill at the folder level so it can be automated during folder provisioning would save a lot of time.

    In our use case, a Salesforce Flow creates a Box folder structure, applies metadata templates, and configures cascade policies. Being able to toggle AI Autofill via API would allow the entire process to run end-to-end without manual steps and avoid maintaining custom AI Extract + metadata upload automation as a workaround.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Box Events API Collaboration Events don't show the same details as the user activity report

    When a User Activity report is generated, we can show events for 'Change user or group role' and 'Removed collaborator'. As part of these records there are additional details provided showing:

    From: ROLE, To: ROLE, Folder ID: 1234
Was: ROLE, Folder ID: 1234

    When using Box Events via API we also see events for COLLABORATION_ROLE_CHANGE and COLLABORATION_REMOVE. These line up to the records in the User Details report however they are missing the details about the previous states of the collaboration.

    As part of our company policy for managing collaborations, I need to be able to fetch the previous roles of users so we can automatically revert these changes (in specific cases).

    I see that the information is being captured, but not passed through to the API for some reason. Generating reports manually each time is not a viable solution, so I'm looking to get these additional details added into the event's additional details dictionary.

    When a User Activity report is generated, we can show events for 'Change user or group role' and 'Removed collaborator'. As part of these records there are additional details provided showing:

    From: ROLE, To: ROLE, Folder ID: 1234
Was: ROLE, Folder ID: 1234

    When using Box Events via API we also see events for COLLABORATION_ROLE_CHANGE and COLLABORATION_REMOVE. These line up to the records in the User Details report however they are missing the details about the previous states of the collaboration.

    As part of our company policy for managing collaborations, I need to be able to fetch the previous… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Support for Hubs Management Endpoints via CLI

    Available via API endpoints, but support does not yet exist for management via the CLI.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. API Endpoint to Customize Collaboration Invitation Email

    Currently, when sending collaboration invites via the API you are unable to customize the message. For collaborators that do not have a Box account, it leads to the invitation message showing:

    "" - FirstName Last Name

    This is unprofessional and often confusing to the individuals receiving the invitation.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Support for fetching and modifying co-admin permissions.

    Support for fetching and modifying co-admin permissions.
    Currently, Box allows users to retrieve a user’s role as an attribute via the /users/{user_id} endpoint. The possible role values are “user,” “admin,” and “coadmin.” While permissions for the “user” role can be accessed through this endpoint, the permissions and privileges associated with the “coadmin” role cannot be retrieved or modified through the API. This functionality is, however, accessible through the admin console user interface.
    https://support.box.com/hc/en-us/articles/360044194393-Granting-And-Modifying-Co-Admin-Permissions

    14 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Support streaming uploads or appendable upload sessions (unknown final size)

    I have a use case where data is generated continuously (sensor readings). I want to build a file in Box by streaming bytes over time and then finalizing the file when the session ends.

    Currently, Box’s chunked upload API requires specifying a file_size up front and mandates a fixed total in each Content-Range header. This prevents uploading content when the final size is not known at the start of the session.

    Request:
    Add support for a streaming or appendable upload workflow, where:

    1. A client can create an upload session without knowing the final file size
    2. Chunks can be uploaded incrementally as data is produced
    3. The file size is determined at commit time, not at session creation

    This would support scenarios such as live sensor feeds or any workflow where file contents are produced continuously.

    Is there an existing workaround or planned support for this capability?

    I have a use case where data is generated continuously (sensor readings). I want to build a file in Box by streaming bytes over time and then finalizing the file when the session ends.

    Currently, Box’s chunked upload API requires specifying a file_size up front and mandates a fixed total in each Content-Range header. This prevents uploading content when the final size is not known at the start of the session.

    Request:
    Add support for a streaming or appendable upload workflow, where:

    1. A client can create an upload session without knowing the final file size
    2. Chunks can be uploaded incrementally… more
    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Copy File using Salesforce SDK

    There are many useful methods in the Box-Salesforce SDK, but it would be helpful to have one for copying a file id to a new folder.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Disable all notifications for an integration/custom app

    Rather than having to disable notifications by passing the specific header, we would like to disable notifications for an application completely by using a toggle or application scope.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Allow Custom Domain Email Addresses for Service Accounts and App Users

    Service Accounts and App Users are automatically assigned an email address with the @boxdevedition.com domain. This becomes problematic when a company's collaboration settings define internal users by their own corporate domain (e.g., example.com).

    Under this configuration, if a shared link's access level is set to "People in your company," the Service Accounts and App Users are treated as external users because their @boxdevedition.com email does not match the company's domain. Consequently, they are blocked from accessing these internal-only links, which hinders automated workflows and API-based processes.

    Proposed Solution
    Introduce a feature that allows administrators to change the assigned @boxdevedition.com email address for Service Accounts and App Users to an email address under a domain owned and verified by their company.

    By enabling this change, these accounts would be correctly identified as internal users within the tenant. This would ensure they can successfully access shared links restricted to "People in your company," allowing for seamless and secure integration with internal automated processes.

    Service Accounts and App Users are automatically assigned an email address with the @boxdevedition.com domain. This becomes problematic when a company's collaboration settings define internal users by their own corporate domain (e.g., example.com).

    Under this configuration, if a shared link's access level is set to "People in your company," the Service Accounts and App Users are treated as external users because their @boxdevedition.com email does not match the company's domain. Consequently, they are blocked from accessing these internal-only links, which hinders automated workflows and API-based processes.

    Proposed Solution
    Introduce a feature that allows administrators to change the assigned @boxdevedition.com email… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. event stream api

    Within the Event stream API, have the ability to filter events by folder ID in the “Get Enterprise Events” API call.

    In addition, add missing data in Response certain event types such as:

    • Folder delete doesn't give file path
    • Copy gives item id of source but not name or link
    • Rename doesn't give source file path
    10 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Use the API to move a file in one Box folder and add it as a version in another folder.

    Use case:
    1. Un-retouched ref sits in Box folder
    2. New version of file comes in from external retoucher
    3. API moves incoming retouched file as version

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Developer Platform  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating