Kloudless Product Updates Roundup: Email, ID Changes, and New Connectors. David Hallinan Published: May 19, 2020 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, Email, 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 some new features and functionality for our products that make integrating with Kloudless even more powerful. So, without further ado, let’s jump in go over some of our new product updates!ID UpdatesWe’ve written at length about the formats that we use for our files and folders in articles here and here. Essentially, when IDs are created in their respective APIs, they are given whatever format that cloud service decides to use. When dealing with a Unified API, however, these discrepancies in ID format lead to an engineering headache when it comes to deciphering which ID belongs to which service. Kloudless formats the ID of these pieces of data into a universal format that is assigned to each file or folder when it is retrieved from the underlying cloud service. An example of an ID after being assigned Kloudless’ format might look something like this: FyeUi9p3CY_WMHfKToZSg5-0f2opUe0rQBoJ69ukvd188=1FyeUi9p3CY_WMHfKToZSg5-0f2opUe0rQBoJ69ukvd188=This approach, while fine for the most part, does lead to a few drawbacks. First, encrypting strings on a per-account basis causes the same object ID to vary depending on which Kloudless account it was accessed through. For example, the same shared file in Box, which Box provides one ID for, could have different IDs depending on which Kloudless account it was accessed through. Even further, it becomes unclear as to what type of ID this format references as it appears as a randomized string of characters. We’re happy to announce that we have updated our ID format to be even easier to use. An example of this new format for a file pulled from a cloud storage service would look something like this: file_dGhpcyBpcyBhIGZpbGUgaWQh1file_dGhpcyBpcyBhIGZpbGUgaWQhThis new approach matches the Kloudless ID to the upstream ID, making it easier to identify the same object, file, or folder in a service even if it’s accessed through different user accounts connected via Kloudless. It also makes it easier to copy/paste since it’s purely alphanumeric with a simple underscore separating the prefix from the string of letters and numbers. Lastly, the prefix has now been changed to relay what type of ID it is. (In the case above, we are looking at a file ID.)Unified Email APIThe Kloudless Unified Email API is officially live and ready to use now. Supporting Gmail, Outlook, and Exchange Server 2013+, the Unified Email API can list and retrieve all mail and attachments from a user’s mailbox, monitor for any new mail that arrives and connect both regular user accounts and admin accounts for org-wide access to data. This brand new Unified API is the culmination of months of hard work, and we can’t wait to see how our customers incorporate it into their products. To read more about the Kloudless Unified Email API, please read our in-depth article here.New ConnectorsAs always, we’re hard at work adding more connectors to our catalog of cloud services. We have a few new ones to announce, as well as some very big names coming very soon. The Kloudless Unified Storage API now supports the Kapost connector, so applications needing integrations with the powerful content marketing software need look no further. We’re also happy to announce that both Zendesk and MS Teams are in alpha-release, so please contact us to learn more and get a jump start on integrating with either of these connectors.More To Come SoonAs I wrote before, we’ve got some very big news on the horizon, but that will have to wait just a bit longer. You can check out our full release notes online. Please send us your feedback on our product updates and let us know what you’d like to see on our roadmap at firstname.lastname@example.org!