Unified Documents Actions

Unified Documents Actions for file and knowledge management across platforms, with consistent data models for drives, folders, and documents.

Benefits of the Documents Actions

Real-Time File & Folder Sync

Built for easily syncing files, in real-time from multiple providers. Use the api to access nested folders & files data in a simple and unified way, regardless of the underlying provider.

Unified File Picker

One File Picker SDK that lets your users pick files from multiple providers, with a single call to the SDK and get back picked files & folders the same way regardless of the provider.

Real-Time Data Synchronization

StackOne’s APIs support real-time synchronization, ensuring that content changes are reflected immediately across connected platforms.

Privacy-First Design Ensuring Compliance

With a focus on security, StackOne ensures secure content storage and maintains compliance with data protection regulations.

Synthetic and Native Webhooks for Updates

The platform provides both synthetic and native webhooks, delivering real-time notifications for changes in drives, folders, and files.

Comprehensive File Management and Knowledge Base Integration Coverage

StackOne offers pre-built connectors with leading File Management platforms, simplifying the integration process.

StackOne SDKs & OpenAPI Specification

Use our official SDKs for faster integration. Build with language-native libraries. Full list here.

OpenAPI Specification

Click here

Popular SDKs

Node.js Java (JVM) PHP Ruby

Entity Model

The Documents Actions are built around three entities: drives, folders, and files.

Entity	Description
Drive	The top-level container — a storage volume, shared drive, or knowledge base space. Each drive can contain folders and files directly.
Folder	A named container within a drive. Folders can nest inside other folders and track their parent (parent_folder_id) and owning drive (drive_id).
File	A document or content item. Files carry metadata about format (file_format), available export types (export_formats), and the default format used when downloading (default_download_format).

Field availability varies by integration provider. Optional fields may be null if the provider’s API does not expose them. See your connector’s integration guide for coverage details.

File formats

The file_format field uses a normalized enum across providers. Common values include pdf, docx, xlsx, pptx, html, csv, png, jpg, and unknown. The export_formats array lists the MIME types available when downloading a file, and default_download_format is the format used when no export format is specified.