Box Integration

Uploads from the Box API support the following types of files:

All file types are selectable. This includes audio, video, image, text, office, and compressed archive files.

Section Quick Jump:

API OAUTH Webhooks

Using the Box API

  1. User selects Box from services list
  2. user authenticates connection by logging into Box account
  3. user is connected and can select files from Box in Filestack dialog

Box api upload widget

Upload from Box

Uploading or "picking" a file from Box in the context of Filestack means choosing a file and creating a distributable link to that file after that file is copied to a new storage location.

Sample Upload Code
client.pick({ fromSources: ['box'], }).then(result => { console.log(JSON.stringify(result.filesUploaded)) })

Create your own Box OAuth application to Connect to Filestack:

By default, you do not need to configure anything to start uploading Box files, Filestack is ready to go out of the box. When a user logs into their Box account from your site, the Filestack company application will show up. You can configure it so that your application shows up instead in order to make a more seamless experience for your customers. So let's get started.

This video walks through the steps listed below

  1. Go to
  2. Sign up or if you already have an account go to My Apps.
  3. Go to (if you already have an application, click “create a box application” in the side bar).
  4. Give your application a name and choose Box Content.
  5. Enter in the redirect_url field under OAuth2 Parameters and hit save.
  6. Copy the client_id and client_secret and go to the developer portal, click on Auth Keys and then enter the client_id under Box App Key and the client secret under Box App Secret, and hit save.
  7. Test to make sure you can connect to your Box app through Filestack.

Congratulations! Your custom Box application is all set up for use with Filestack!

Box Webhooks for Your Application

Box Webhooks serve the purpose of notifying users about events that occur in relation to their Filestack account. In your developer portal, you can set one or many urls whose purpose is to receive the messages triggered by specific Filestack events.

These are the three event types that will send messages to your webhook url(s) concerning Box:

  • Box File Uploads
  • Box File Exports
  • Box File Conversions

Configuring Box Webhooks

Filestack Webhooks are configured in the developer portal under Credentials > Webhooks. If you enter your url and select "All", then one entry will be made for each type of Filestack Webhook Event, including the ones for Box. To learn more about configuring and receiving webhooks please visit our main webhooks documentation page.

Receiving a Box Webhook Notification

Configuring your server to receive a new webhook is the same as creating any page on your website. If you are using Sinatra, add a new route with the desired URL. In PHP you could create a new .php file on your server. It doesn't need to be complicated. With webhooks, your server is the server receiving the request. You can even use an external service such as RequestBin as shown in the screenshot above.

Webhook data is sent as JSON in the request's body. The full event details are included and can be used directly. The "action" in the JSON is the type of Filestack event that happened, be it a file being uploaded, or simply the Filestack dialog opening.

Filestack will retry sending a webhook 3 times if the first attempt fails. The second attempt to deliver a webhook happens 5 minutes after the first attempt, the third attempt happens after 1 hour, and the final attempt to deliver a webhook happens 12 hours after the first attempt.

Note that for file uploads, both symlinks and files copied with pickAndStore, the "client" field shows the service used.

For conversions, the "provider" shows where the file resides. If the file was stored to Filestack's storage, the provider will be "internal", otherwise it could be "amazon" if the original was stored to S3, or one of the cloud drives Filestack connects to, such as "Box" if the link to the file was a symlink.

The following are examples of what the Box specific webhook messages include and look like:

  1. File Upload (symlink):

  2. {

  3. File Upload (with store):

  4. {

  5. File Export (save to):

  6. {
      "action": "fp.export",
      "timestamp": 1444257665,
      "id": 142447,
        "source": "",
        "client": "Box",
        "filename": "newFiletest.jpg",
        "created": ""

  7. File Conversion:

  8. {