WebDAV Integration

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

  1. User selects WebDAV from services list
  2. user provides Hostname, Username, and Password
  3. user is connected and can select files from their WebDAV server in Filestack dialog

WebDAV api upload widget

Upload from WebDAV

Uploading or "picking" a file from WebDAV in the context of Filestack means choosing a file and creating a distributable link to that file where it exists in WebDAV. This is the Filestack URL that all "Pick" functions return. If you are using the pickAndStore method, then the file from WebDAV is copied to a new storage location.

Sample Upload Code
filepicker.pick( { mimetypes: ['*/*'], services:['WEBDAV'], }, function(Blob){ console.log(JSON.stringify(Blob)); } );


By default, you do not need to configure anything to start uploading files from WebDAV, Filestack is ready to go out of the box. When a user logs into their WebDAV account from your site, the Filestack company application will show up. Custom OAuth Applications for WebDAV are currently not supported in Filestack

WebDAV Webhooks for Your Application

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

  • WebDAV File Uploads
  • WebDAV File Exports
  • WebDAV File Conversions

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

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

The following are examples of what the WebDAV 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": "https://www.filestackapi.com/api/file/qHi4LxRh28IeEBdJcFpw",
        "client": "WebDAV",
        "filename": "newFiletest.jpg",
        "created": "https://www.filestackapi.com/api/file/s40jJOQDGVr2T86cgOAe"

  7. File Conversion:

  8. {