ExaVault has had an API for a bit now and have seen customers deeply integrating our services directly into their applications, while retaining all the features that we provide with our web interface and FTP accessing capabilities.
Every once in awhile, we get the question “Why would I want to use this? What could it do for me?” The short answer is nearly anything, but that’s not a very satisfying answer (and an even worse blog post!) Today, we’re going run down a little about what the API is and what you can do with it.
To begin, let’s define what we’re talking about. API stands for Application Program Interface and what it lets you do is write code that directly talks to ExaVault. Anything you can do from our web interface, you can do via our API, which in turn means you can do it programmatically.
What can you do? Well, you can upload or download files, create or edit shares, create users, move files around, get activity logs and much more. You can see the full list of commands here.
Still confused? Let’s get into the examples. Let’s say you’re a musician (with spiky punk rock hair) and you want to create a way for musicians to easily collaborate with complete strangers by sharing audio-takes and having others add on? You could use our API to store those files in ExaVault, and you could control 100% of your users experience - you would be able to control the accounts, the virtual bands, everything and make it seamless for your users. In terms of what the API would be doing in this example, you would be creating folders, creating new users, and storing their files in their folders.
Let’s look at another example. You run a print shop (and have normal, human hair) that works entirely online. As a part of your website, you have to get the files that need printed from the customers. Sure, you could use our Uploader Widget, but you want more. When a customer enters an order, you want everything about the order to be contained in a folder so the people downstairs in the printing area don’t get confused.
In this example, you could go through our API to create a new folder for each customer, and a folder inside of each customer's folder with a new folder per order. You can store the files that need uploaded in that folder, as well as their contact information and shipping address that you collected as a part of the order process in a text file with the files.
There are many other examples, and many different hairstyles that could go along with those examples, but we hope you get the idea. If you can dream it up, you can do it with our API. If you’d like to get started using our API, visit our introduction page and get to coding.