Unified API
Unified File Storage API
One standardized interface to read and write cloud storage data across every provider. 10 unified resources, 9 supported integrations, zero provider-specific code.
Unified resources
Supported integrations
Real-time, no data storage
Data Model
File Storage resources
Every resource is normalized across providers. Use the same schema whether your customer is on Box or Dropbox - Business.
Drive-items
Drive Items are the files and folders present in a file storage system. These items are usually part of a Drive. You can differentiate between files and folders using the type attribute.
Drives
Drives is a collection of files and folders. They could have multiple Drive Items within them. Users could have multiple Drives accessible to them in a file storage system.
Files
[DEPRECATED] The file represent a file in File Storage.
Folders
[DEPRECATED] The folder represent a folder in File Storage.
Groups
Groups represent a collection of users. They could be grouped based on departments, projects, permissions, etc.
Permissions
Permissions can answer your questions around which User has access to do what on a Drive Item or a Drive.
Tags
Represents the tags in a file storage system
Users
Users represent the people using the underlying file storage system.
Webhooks
Workspaces
Workspaces represent the top-level subdivision in a file storage system. They usually have their own set of drives, groups and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc.
Integrations
9 integrations, one API
Connect to any of these providers through the Unified File Storage API. Same resources, same schema, same code.
How It Works
From zero to integrated
Go live with the Unified File Storage API in under an hour. No boilerplate, no maintenance burden.
Connect your customer’s account
Use Truto’s pre-built auth flows to connect any cloud storage provider. OAuth, API keys, and custom auth — all handled.
Query the unified API
Read and write data through a single, normalized REST API. Same endpoints, same schema, regardless of the underlying provider.
Customize with JSONata
Need a field the unified model doesn’t cover? Extend the schema with declarative JSONata mappings — no code deploys, no waiting on us.
From the Blog
File Storage integration guides
Deep dives, architecture guides, and practical tutorials for building cloud storage integrations.
How to Integrate Google Drive, SharePoint, and Box: What It Really Takes
Explore the engineering trade-offs of building Google Drive, SharePoint, and Box integrations versus using a Unified File Storage API.
Moving Past Checkboxes: Automating Immutable Policy Evidence
Simple checkboxes for policy acknowledgement no longer satisfy enterprise auditors. Learn how to automate legally binding e-signatures using Unified APIs.
Challenges we face while building integrations: SharePoint
Discover the real-world engineering challenges of building a SharePoint integration, from Graph API limitations to complex permission hierarchies and sandbox setups.
The Unholy Mess of File Picker APIs (and How We Tamed It)
Implementing native cloud file pickers for Google Drive, OneDrive, and Box is an architectural nightmare. Here is how we unified them into a single API.
Your Unified APIs Are Lying to You: The Hidden Cost of Rigid Schemas
Standard unified APIs force you into rigid schemas and black-box architectures. Learn why engineering teams need a programmable integration layer with raw API access.
How to Integrate with the SharePoint API: 2026 Architecture Guide
A technical guide to integrating with the SharePoint API in 2026 — covering Microsoft Graph hierarchies, OAuth with Entra ID, File Picker v8 pitfalls, rate limits, and pagination.
Unified File Storage API
Start building with the Unified File Storage API
9 integrations. 10 unified resources. Zero provider-specific code. Ship cloud storage integrations in hours, not months.
Talk to us