Here at Kloudless, a considerable amount of our time is spent on making our Unified APIs as robust as possible. We aren’t content with our work until we feel like we can offer our clients an unprecedented level of functionality from our unified endpoints. Whether it be Storage, Calendar, or CRM services that our customers need to integrate with, we want developers using our products to feel like they won’t miss out on any functionality that would be provided by natively integrating with an API.
In that vein, we’re happy to announce that our Google Drive connector has been updated to incorporate all of the changes and functionality in the API’s new v3 update.
The v3 update of the Google Drive API is not an especially large one, but it does contain quite a bit of change when it comes to the objects being returned themselves. The greatest change to the objects is due to a user-facing feature of Google Drive that was added recently: the removal of Team Drives.
Team Drives have been renamed to Shared Drives, and while the functionality has remained essentially identical, some key/value pairs on the JSON returns from Google Drive have been deprecated. Any key name that refers to the old Team Drives has been deprecated, including teamDrive and teamDriveId. The only other change reflected on the JSON objects is the deprecation of the type key, which has now been given a new key of changeType. The functionality, like with the Team Drive counterparts, remains the same, but the language has been updated for clarity.
Besides the makeup of the objects themselves, there are a few new methods available to retrieve information from the API:
- getStartPageToken: Gets the starting pageToken for listing future changes.
- list: Lists the changes for a user or shared drive.
- watch: Subscribes to changes for a user
That about does it for new functionality in the update. So why does it matter that Kloudless updated its connector when so little functionality was added on Google’s side?
Kloudless Software Engineer, Meng-Hsin Tung, was in charge of the updates on Kloudless’ end when it came time to update our Google Drive connector. In order to properly account for the changes in the API, Meng-Hsin approached the update methodically. First, he summarized all the Google Drive API v3 changes to properly plan how our unified abstraction would accommodate the new key/value pairs. He then meticulously leveraged the tests in place to ensure that the behavior wouldn’t change once the new metadata had been added. Finally, he went through a rigorous code review to make sure that no uncaught bugs made it to production after all of the new functionality had been incorporated.
All of this hard work was done for the sake of our customers with connections to Google Drive already in place. Kloudless’ Unified APIs are constantly updated with new features and functionality for all of our connectors. Our customers only have to build a single connection to the Unified API of their choice, and then rest assured that all future maintenance and updates will be performed on Kloudless’ side. Customers can now enjoy the new functionality and changes in v3 of the Google Drive API without changing a single line of code.
Driving Into the Sunset
Whether you need any of the additional functionality added to Google Drive in your application is irrelevant. When a response object changes, your code will break in most circumstances, regardless of whether you plan on using any of the added functionality. This is a common issue when it comes to keeping your API integrations sound. If an API updates its version, there is commonly enough of a change in the response that your application’s connection to the API will no longer work as intended. As a result, software developers are often caught having to implement fixes quickly whenever an API changes.
The Kloudless Unified Cloud Storage API provides connections with Google Drive, Dropbox, Box, Egnyte, and more. By connecting to Kloudless, an application can add cloud storage service integrations to their software product without building and maintaining each one individually. This gives engineering teams working on API integrations the ability to get to market faster and vastly reduce future maintenance.
Whether you’re in the process of planning your product roadmap, or you’re hoping to fix your bespoken cloud storage API integrations, we have the integration solutions that your codebase demands. To help you get started, we have put together a comprehensive guide full of helpful strategies, tips, and articles to get you started with using the Kloudless Unified Cloud Storage API.
Download our guide here, and start taking the pain away from your application’s cloud calendar integrations!