Kloudless API v1 Launches Today

Last week, we launched our Universal CRM API. You can read more about the announcement here. The new API kicks off our broader product strategy to provide Universal APIs for many important areas of business.

As part of this product launch, we are also launching v1 of our API. Our goal with v1 is to establish a strong foundation for building future products and functionalities.

 

What’s new in v1

The migration to v1 introduces new capabilities and improvements to existing functionality.

Universal CRM API
Previously, the Universal CRM API was only available in Kloudless Enterprise. With v1, the CRM API is available to any developer that prefers to use our cloud version at kloudless.com. You can start integrating the CRM API for free here.

OAuth 2.0
We are introducing a standards-compliant OAuth 2.0 authentication mechanism to connect user accounts, which enables easy integration with other tools that support OAuth 2.0. Other benefits include:

  • Documented support for out-of-band, authorization code grant, and implicit grant OAuth 2.0 flows to support authentication in any environment.
  • More granular scopes to better control the services, APIs and types of accounts users can connect to your app.
  • Improved security with white-listed Redirect URIs, validated Client IDs/Secrets, and verified Bearer tokens.

Read more about Kloudless authentication here.

Other enhancements
As you read through our documentation, you will find small improvements to many endpoints. For example, we’ve updated our old permissions format to support groups and our old pagination format to be more flexible.

 

What this means for you

First, any new applications you develop should use API v1.

Second, there are backwards incompatible changes in the migration from v0 to v1. API v1 is built thoughtfully, and we try to limit the changes you need to your implementation to only the things we consider most important moving forward. You should update your app’s integration with Kloudless as soon as possible.

Here is a summary of the backwards-incompatible changes.

API-namespacing for endpoints
All endpoints specific to the Storage API have been namespaced under /storage/. Learn more

OAuth 2.0 Authentication
OAuth 2.0 authentication is now required. The previous authentication format is no longer supported. OAuth 2.0 Bearer tokens have replaced Account Keys. Learn more

Events
Deprecated event object attributes have been removed. Learn more

Pagination
next_page must be used to identify the next page value for pagination. Learn more

File Uploads
Files are uploaded as binary content rather than via multipart form POST requests. Learn more

Permissions
File/Folder permission updates take in a list of permission objects rather than a mapping of user emails to roles. Learn more

Users of the UI Tools do not need to make changes to use v1, although they would have to make changes to switch to OAuth if using the Authenticator JS library or if using Account Keys from the File Explorer.

None of your users need to re-authenticate when you switch your app to either OAuth 2.0 or the v1 API.

 

Deprecating v0 and the old auth mechanism

As of today, v0 of the API is deprecated. In order to provide you with the most up-to-date features and support a single, consistent API platform, we’ll be turning off API v0 on February  28, 2018.

Our previous authentication mechanism will be turned off in one year on August 31, 2017.

In our next update, we will provide a more detailed deprecation timeline.

We love building for the thousands of developers using our platform. If you have any questions or feedback, we’d love to hear from you in our developer forum.

How to connect with 1.2 billion Microsoft users

Last week at the Connect(); conference in New York, Microsoft publicly unveiled the Microsoft Graph, a unified API that enables developers to tap into Microsoft’s 1.2 billion users around the world.

There is a lot going on in the Microsoft Graph, but we will look closely at the file storage services: OneDrive (OD), OneDrive for Business (ODB), and SharePoint Online (SP).

What is the Microsoft Graph

Microsoft Graph is a unified API for connecting to Office 365.

Previously, each Office 365 service was silo’d and had its own unique API. This required developers to obtain separate access tokens and call different endpoints for each service they wanted to integrate with.

With the new unified API, features, data, and insights across Office 365 services can all be accessed from a single API.

That’s nice but..

Historically, Microsoft has not been great with APIs. Services often have multiple versions, each with multiple APIs spanning hundreds of pages of documentation.

Our implementations of OD, ODB, and SP pull from several different APIs in order to get comprehensive feature and data coverage. Of course, developers that use Kloudless are shielded from this complexity, since we offer a universal interface for integrating file storage services.

Getting started

If you’re not a Kloudless developer yet, this means that you’ll have to go through another proprietary API, integrate it into your application, and maintain it in the long run. You can read through the documentation and try out the Microsoft Graph at graph.microsoft.com.

If you have an existing integration with Office 365 service, make sure to check for feature parity between the old APIs and the new unified API before overhauling you current implementation.

We noticed several differences. Some features like adding an admin user as a site collection administrator SP are only found in the old SP APIs. Other features like listing all site collections (SP) and personal sites (ODB) are only available in the new Microsoft Graph API.

For use cases that only require basic operations, you’ll be fine switching over to the new API. Otherwise, like us, there’s a good chance you’ll find yourself mixing and matching APIs to get everything you need.

If you are using Kloudless, you’re already integrated with the Microsoft Graph! We’re dedicated to bringing you the latest and greatest, so we worked with Microsoft earlier this year to get our hands on a preview of a couple unreleased APIs, including the Office 365 Unified API.

As a result, no extra work is required to transition to the Microsoft Graph, because we’ve taken care of everything under the hood. You will automatically receive all the improvements and new features.

New features supported in Kloudless

You can access new Microsoft features via the respective Kloudless endpoints.

Events and Notifications (ODB, SP) – Real-time notifications for what’s changed in a folder.

Permissions (OD, ODB, SP) – Adding, modifying, and removing permissions on files and folders. (Coming soon)

What we think about the new Graph

We like all the talk coming out of Redmond. Unifying APIs is a mission that we can get behind.

However, a few challenges remain if you’re looking to integrate file storage APIs into your application:

  1. Uniform APIs are a great promise, but execution and timeliness matters. A few years in, OneDrive and OneDrive for Business still have many API differences.
  2. It sounds like a lot of updates are planned. If you plan on integrating directly with the new API, be prepared for several rounds of maintenance work in the near future.
  3. The Microsoft Graph will not unify the other 25+ file storage APIs like Box, Dropbox, Google Drive, Egnyte, etc.

This is definitely a step in the right direction for Microsoft to endear themselves with developers. It certainly makes our job a bit easier.

Kloudless unifies 25+ file storage services under a universal API. If you’d like to easily integrate the Microsoft services and many others, sign up for a Kloudless account and start developing for free!

1947 partnership

Working with The 1947 Partition Archive to Record Oral Histories

At Kloudless, it’s awesome seeing all the cool stuff being built on our API. Once in a while, we get the opportunity to work with a nonprofit organization with an amazing philanthropic mission.

Today, I’m thrilled to announce that we’ve partnered with The 1947 Partition Archive to make recording oral histories easier for everyone around the world.

1947 partnership

The 1947 Partition Archive is a crowdsourced collection of oral histories documenting the Partition of British India, the largest mass refugee crisis in the history of the world. The organization provides a platform to “collect, archive and display oral histories that document not only Partition, but pre-Partition life and culture as well as post-Partition migrations and life changes.”

The Kloudless team is excited to help in this effort by making it easy for oral history collectors around the world to contribute their stories to the Archive. The Kloudless gives the Archive a user-friendly tool to accept video files of any size and resume paused uploads, which is especially important in areas with unreliable internet connections.

At Kloudless, we believe that those doing good have enough on their plates and shouldn’t have to deal with the complexities of file uploads or any other file/storage features. Nonprofit organizations committed to charitable missions are eligible for heavily discounted or completely free service!

Contact us at hello@kloudless.com to learn more about how we work with nonprofits.