Box Platform

Hello, I’m using the Box API with Python and the boxsdk module. I have developed a system that does the following: when a user uploads a file to a specific folder, a “FILE.UPLOADED” webhook is sent to my server. Then, my server sends a request to rename the file using the file.update_info(data={'name': 'some name'}) instruction. This works. In this case, I need to rename my files with the same name but with a suffix indicating the file number. For example: “file_1.png”, “file_2.png”, “file_3.png”… However, when a user uploads multiple files at once, these requests happen very quickly. My system checks if a file with the same name already exists before attempting to rename the file. If it does, it tries with a higher index suffix: 1, then 2, then 3, and so on. It’s possible that my script doesn’t find a file with the same name, and then, in the time interval between the test and the request to rename the file, another file is renamed with that name. This results in a 409 status error (“

My company does not allow us to share a box folder with any other users or service account. How can I give access to box folder with service account created by my company and not by Box(automation user svc account). Basically, I don’t want to use svc user auto generated by Box upon authorisation but I want use box apis to upload the file. How can I do this? I really need answer to this as soon as possible. Thanks in advance.

Hi all, I create an application and I use private / public key for authenticate. I use .net sdk to upload a file, create a sign request to 1 email and everythinks works fine. After that I recieved the email to sign the document and I can sign it, but after signing the document the sign request is never validated. I don’t have any other emails about errors. Is there a way to have the sign request status ? I try to do the same process manually and it’s work. Did I miss something ?

Please find attached a recording, summary and resources from our most recent Box for Salesforce roundtable here We would like to express our gratitude to Don Hammons of mxHero, Kyle Adams, and Shawn Shay from Box for their excellent presentations. We also extend our thanks to the guests who joined us. Highlights. Recording here Overview of Box automations available in Salesforce Demo of Box Sign for Salesforce mxHero Overview of email management from the cloud and demo of Mail2Sign mxHero LLM AI integration with Mail2BoxSign Box Sign Roadmap (21 CFR Part 11 Compliance, and other updates coming soon)

Is there an easy way to get the number of pages of box file using a native Box api?

Hello, From https://developer.box.com/guides/api-calls/permissions-and-errors/rate-limits/ I can see there are monthly API max limits by customer. Where can I go to see my account’s current API usage towards this monthly cap?

In my previous post, I explored the topic of Box Node.js authentication with OAuth 2.0. Now let’s jump into another method that includes JWT, server-side authentication. It is the most common way to authenticate to the Box API. This is a companion discussion topic for the original entry at https://medium.com/box-developer-blog/authenticate-box-node-js-sdk-with-jwt-47fdd3aeec50?source=rss----a995c24848a3---4

We are currently implementing a functionality to automatically create a Box folder upon record creation in Salesforce. However, we are facing an issue where the folder creation process does not occur (no folder is created, and the return value is NULL) when using the createFolderForRecordId method from the Salesforce Developer Toolkit within an after insert trigger on record creation. We have confirmed that the process works correctly and the folder is created when manually triggered from the Developer Console. Could you please provide guidance on the possible cause of this issue? If it is not possible to achieve automatic folder creation within the trigger, could you please suggest an alternative solution for resolving this requirement? I got a error message as below. 18:18:41:463 USER_DEBUG [572]|DEBUG|Unable to create folder for record id a0E1m000007S0gcEAC - Details: Unable to use default credentials to make a callout to Box (maybe this is in a trigger, constructor, or after a DML

Could you please provide guidance on how to use the API (Update metadata instance on folder:PUT) using Apex? For Create metadata instance on folder(POST), I was able to achieve it as described above. However, I’m unsure how to set the Body for Update metadata instance on folder. Sample Code for Use Create metadata instance on folder(POST) box.Toolkit toolkit = new box.Toolkit(); String folderId = project.ProjectFolderId__c; Map<String, String> metadata = new Map<String, String>{ ‘masterdefkeyword1’ => project.Keyword1__c, ‘masterdefkeyword2’ => project.Keyword2__c, ‘masterdefkeyword3’ => project.Keyword3__c, ‘projectsupplementkeyword1’ => project.SupplementKeyword1__c, ‘projectsupplementkeyword2’ => project.SupplementKeyword2__c, ‘projectsupplementkeyword3’ => project.SupplementKeyword3__c }; String scope = ‘enterprise’; String tempName = ‘projectmetadatatemplate’; // Box endpoint(Create metadata instance on folder) String endpoint

Hello all, Currently, I’m trying to utilize Box to upload/download documents using Nodejs on the backend to do this. From my understanding, I would need to get an access/bearer token (from: https://api.box.com/oauth2/token) - which I’m able to do using Client ID and Client Secret, and once I have the the bearer token I can make API calls as needed. However, I’m trying to test a few of the API calls using postman and receiving an error when doing it this way. As an example, to list the current items in a folder I’m making a GET request in Postman to: https://api.box.com/2.0/folders/:folder_id/items where I’m setting :folder_id to 0. I receive this error that says: { "type": "error", "status": 404, "code": "not_found", "context_info": { "errors": [ { "reason": "invalid_parameter", "name": "folder", "message": "Invalid value 'd_215579098453'. 'folder' with value 'd_215579098453' not found" }

Hi everyone, I’m new here and would appreciate your help with some questions I have about the Content Explorer. I’m trying to set it up so that the preview opens when I double-click an image in thumbnail view. Is there any way to achieve this? Currently, the preview only opens when I click on the filename or a button. I set ‘select’ for the event in addListener, but it’s triggering when I hit other buttons like the ‘share’ button. Is there a way to limit the ‘select’ event to only when a file is selected? Also, what would be the way to make the preview open again when clicking on the same file? Thanks for taking the time to read this Apologies in advance if I’ve posted this in the wrong topic, as this is my first time here.

@matt.riley Could you share thoughts and/or tips on how to automatically apply metadata to file uploads done through the “File Request” feature? The use case is wanting file request uploaders to upload specific types of documents in each separate upload field and to automatically apply a metadata label to the upload done in that field. For example, a File Request form with a Diploma field and a Resume field, upon upload / completion of the File Request those uploads would be tagged in metadata as diploma and resume, respectively. Thus later we could search by metadata for diploma and get all diploma uploads but not resumes, and vice-versa. As a side note, I find metadata in Box confusing because of the requirement to create a “template” which is unusual compared to other tools where one can just create and define metadata independently.

I have created an application as the documentation says, but I always get this error. https://developer.box.com/guides/authentication/client-credentials/ This is your documentation, can you help me? This is my app client id: alhd08bt4pv1gt6n9i4ipi8andjscofb curl -i -X POST "https://api.box.com/oauth2/token" \ -H"Content-Type: application/x-www-form-urlencoded"\ -d"client_id=alhd08bt4pv1gt6n9i4ipi8andjscofb"\ -d"client_secret=*****"\ -d"grant_type=client_credentials"\ -d"box_subject_type=user"\ -d"box_subject_id=2629647****" Response { "error": "invalid_grant", "error_description": "Grant credentials are invalid" }

At the beginning of June, Box Platform launched a new brand API to manage mapping folders in Box to channels in Slack, and also recently launched a new scripts for admins and developers to complete repetitive tasks using the Box CLI. Today, we are releasing a new automation template script using the integrations mappings for Slack API. This is a companion discussion topic for the original entry at https://medium.com/box-developer-blog/new-box-cli-automation-template-to-manage-slack-integration-folder-mappings-a174f9985768?source=rss----a995c24848a3---4

Was trying to create an app user following this guide, developer.box.com App Users - Box Developer Documentation Explore the Box APIs and SDKs to use for app development, API documentation, developer support resources, and access the Box Developer Console and with the following api request: POST - https://api.box.com/2.0/users request: {“is_platform_access_only”: true , “name”:“test”} response: { “type”: “error”, “status”: 403, “code”: “access_denied_insufficient_permissions”, “help_url”: “http://developers.box.com/docs/#errors”, “message”: “Access denied - insufficient permission”, “request_id”: “avrw5xhevqe1xti8” } What is missing? Can you please assist? (I have verified I have sufficient permissions to create a user which is not an app user and it was created successfully) Thanks

最近Boxが開催した社内ハッカソンに、Box API用のRustクライアントを作成するというアイデアで参加しました。この演習には3つの目標がありました。Rustは、システムプログラミング用に特別に設計された堅牢な言語です。多くの利点があります。RustでBox APIクライアントを構築することで、メモリの安全性、パフォーマンス、並行処理と並列処理、開発者の生産性、クロスプラットフォームの互換性など、主要な機能を活用できます。 This is a companion discussion topic for the original entry at https://medium.com/box-developer-blog/rusty-box-box-api%E7%94%A8rust%E3%82%AF%E3%83%A9%E3%82%A4%E3%82%A2%E3%83%B3%E3%83%88%E3%81%AE%E4%BD%9C%E6%88%90-5948c3f1bc2d?source=rss----a995c24848a3---4

Hello, I am using Box API Python SDK to list files. The metadata of files is important for my work. The files in the source folder are uploaded by myself and I am in UTC+09:00 timezone. But when I list the files using the API, all the timestamps returned by the API are in UTC-07:00. Please let me know if that is the default case? or is there anything I can do. SDK Version: 2.7.1 API: client.search.query(...) Thank you 🙂

I’m trying to build some features using the Folder Lock API: https://developer.box.com/reference/post-folder-locks/. However, when I try to do a simple curl POST command to lock a folder, I always receive a 404 “not_found” regardless of the folder I pass to it. The GET command works fine and obviously returns an empty array since I haven’t successfully locked a folder yet, but I know the endpoint and my access token works fine. Are there other exceptions to this feature that aren’t documented? I have ensured I am the sole owner of the folder (no co-owners), but it has been shared with others a Editors. For added detail, I am using the Oauth 2.0 method for access. Any help/guidance on locking folders via the API would be much appreciated!

Hello, I am having issues using the box-ui-elements React package. I have gotten the other “simpler” react components to work correctly with a developer token, but for w/e reason the ContentPreview component never renders the preview of the file. There are 0 errors in the console and if I enable the header it is able to display the file name correctly. So, the file ID is correct and the dev token is accurate since it works with other components on the same screen. Is this a known issue? It doesn’t seem like a sizing issue since it’s given plenty of space and the other components work just fine. Is there a working example repo I could run and supply my dev token & file ID to and see if it works? I ended up just using the raw JS CDN approach that some of the Docs outline to display the ContentPreview and that works just fine. So, I ended up just removing the entire box-ui-elements package since it wasn’t buying me much. I would like to actually use the package though since it is simp

Hi Rui, Thank you very much for your answer. This is exactly what I was looking for. Now I think the way to achieve my goal is to create a webhook with ‘COLLABORATION.ACCEPTED’ trigger, that way I can assign the approval task to the user. So I need the user id to assign the task. But is ‘collab.id’ the user id? The API documentation doesn’t say so but I note that you wrote ‘Collaborator:’. Cheers