“If we always helped one another, no one would need luck.”
We’re back with another helpful post centered on helping you overcome some of the most commonly asked questions about the APIs we work with here at Kloudless. Every Monday, we will aim to help answer some of the oft-asked inquiries into the world’s most popular APIs. Today, we will be turning to another of the industry’s top names when it comes to file storage: Box.
Many of our reader’s questions regarding Box are aimed at how often the API can be requested to before a call rate limit kicks in. There are a handful of rules in place for accessing the file storage API, but it isn’t always clear which limits overlap with one another. We’re here to sort you out once and for all.
Let’s walk through how Box goes about setting their rate-limiting!
Box’s reference docs layout the rate limits in place, but there are four different guidelines to follow in order to not go over the limit. Those rate limits are as follows:
- 10 API calls per second per user.
- 4 uploads per second per user.
- 6 searches per second per user, up to 60 searches per minute.
- 12 searches per second per enterprise.
Keep in mind that the 10 API calls per second per user is inclusive of the 4 uploads, so they will count towards the individual limit. So, for instance, you can make 4 API uploads as well as another 6 calls per second before going over the limit.
Calls to search are capped at 6 per second, so ensure that you are staggering your calls to not go over the allowed search calls per second or minute.
The only thing that can end up being a bit tricky is the 12 searches per second that enterprise accounts are allowed. This number applies to the whole organization, but individual apps on the account will still be governed by the rate limits per individual user. Therefore it is necessary to observe the number of calls across all apps belonging to an organization, so as to not go over either rate limit in place.
That’s it! Abide by these rules, and you will be able to take full advantage of all of the functionality Box’s API has to offer. If your organization is considering adding Box functionality in your application, keep in mind the benefits of adding as many file storage providers as possible. If your users are ingrained in another file storage provider like Dropbox, Egnyte, or Google Drive, they may forego your application entirely in search of a competitor that provides the connection to their preferred service. Give your users the choices they need, while bolstering your own application’s functionality, with the use of a Unified API from Kloudless. You can offer your users dozens of file storage services in the same amount of code it would take to connect to a single API. On top of that, when response formats change or APIs update their access endpoints, a Unified API handles all the future maintenance necessary to keep functionality working. To learn more about the Kloudless Unified Storage API, please download our free guide to storage integration strategy today!