OneDrive Integration

Uploads from the OneDrive 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 OneDrive API

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

OneDrive api upload widget

Upload from OneDrive

Uploading or "picking" a file from OneDrive 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: ['onedrive'], }).then(result => { console.log(JSON.stringify(result.filesUploaded)) })

Create your own OneDrive OAuth application to Connect to Filestack:

By default, you do not need to configure anything to start uploading files from OneDrive, Filestack is ready to go out of the box. When a user logs into their OneDrive 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 fill out an application name and agree to the terms of use
  2. On the next page enter as the redirect uri. The other fields are optional but we recommend adding a logo if you want.
  3. Next copy the Application ID and Application secret from the same page, then go to the Filestack developer portal and click on Auth Keys, scroll down to the bottom and enter the Application id and the Apllication secret into the skydrive fields and click save
  4. Go and test that you can connect to your OneDrive application through Filestack

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

OneDrive Webhooks for Your Application

OneDrive 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 OneDrive:

  • OneDrive File Uploads
  • OneDrive File Exports
  • OneDrive File Conversions

Configuring OneDrive 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 OneDrive. To learn more about configuring and receiving webhooks please visit our main webhooks documentation page.

Receiving a OneDrive 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 "OneDrive" if the link to the file was a symlink.

The following are examples of what the OneDrive 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": "OneDrive",
        "filename": "newFiletest.jpg",
        "created": ""

  7. File Conversion:

  8. {