Integrating Box with Superblocks seamlessly merges robust file storage and collaboration capabilities. Connect with Box's API to craft tailored workflows, automate file management tasks, synchronize data across applications, and elevate your team's productivity seamlessly.
Setting up Box
Create an access token
To begin using Box's API, follow these steps:
- Log in to your Box account
- Navigate to the Developer console and click Create New App
- Choose Custom App then provide a name and any other configuration information
- Click Next, followed by User Authentication (OAuth 2.0) and Create App
- On the Configuration tab scroll to OAuth2.0 Redirect URI and paste Superblock's callback URL
- Add application scopes
- Copy the Client ID, Client Secret, and scopes into your integration's configuration
- To generate a shared token, click Connect to Box or uncheck the shared token option so Application users will be prompted to log in
Learn more about Box API authentication.
Once you have an access token, you're ready to set up your Superblocks integration.
- In the web app, navigate to the Integrations page
- Click on the Box tile
- Name the integration
- Paste your credentials into the relevant fields
- Optionally, add more configurations to set credentials for different environments
- Click Create
Use Box in APIs
Once your Box integration is created, you can start creating steps in Application backend APIs, Workflows, and Scheduled Jobs to call Box API actions. Box actions are REST requests. To learn more about REST requests in Superblocks, see the Building REST requests guide.
Get file informationRetrieves the details about a file.
Restore fileRestores a file that has been moved to the trash. An optional new parent ID can be provided to restore the file to in case the original folder has been deleted.
Update fileUpdates a file. This can be used to rename or move a file, create a shared link, or lock a file.
Delete fileDeletes a file, either permanently or by moving it to the trash. The the enterprise settings determine whether the item will be permanently deleted from Box or moved to the trash.
Download fileReturns the contents of a file in binary format.
Upload file versionUpdate a file's content. For file sizes over 50MB we recommend using the Chunk Upload APIs. # Request body order The `attributes` part of the body must come **before** the `file` part. Requests that do not follow this format when uploading the file will receive a HTTP `400` error with a `metadata_after_file_contents` error code.
Upload fileUploads a small file to Box. For file sizes over 50MB we recommend using the Chunk Upload APIs. # Request body order The `attributes` part of the body must come **before** the `file` part. Requests that do not follow this format when uploading the file will receive a HTTP `400` error with a `metadata_after_file_contents` error code.
Create upload sessionCreates an upload session for a new file.
Create upload session for existing fileCreates an upload session for an existing file.
Get upload sessionReturn information about an upload session.
Upload part of fileUpdates a chunk of an upload session for a file.
Remove upload sessionAbort an upload session and discard all data uploaded. This cannot be reversed.
List partsReturn a list of the chunks uploaded to the upload session so far.
Commit upload sessionClose an upload session and create a file from the uploaded chunks.
Copy fileCreates a copy of a file.
Generic HTTP Request
Every SaaS integration in Superblocks comes with a built in Generic HTTP Request Action. This is a powerful action you can use to call Box API endpoints not in the Superblocks supported actions.
To use this action simply add the method, path, required query parameters, and body for the desired endpoint.
Learn more about REST requests in Superblocks in our Building REST requests guide.
Generic HTTP Requests use the authentication set up and base URL you've configured for your integration, making it an easy for your team to extend Superblocks Integrations to meet their needs.