Documents
Overview
The StackOne unified API for Documents streamlines access to knowledge bases (e.g., Notion, Confluence) and file storage platforms (e.g., Google Drive, SharePoint), enabling seamless retrieval, uploading, and downloading of content. By abstracting away platform-specific complexities, it simplifies integration while ensuring secure and efficient document management across multiple systems.
Benefits of the Documents API
Here are some benefits of using our Documents API that simplifies and enhances the recruitment process:
Entity Model and Relationships
The following diagram illustrates the key entities within the Documents API:
The following table outlines key entities within the Documents system and provides a brief description of each:
Entity | Description |
---|---|
Drives | Represents the top-level storage containers in the document management system. Each drive can contain multiple folders and files, and has basic metadata like name, description, and URL. Drives are typically used to organize content at the highest level, such as by department or project. |
Folders | Manages hierarchical organization within drives. Folders can contain files and other folders (subfolders), creating a tree structure. Each folder tracks its owner, parent folder, associated drive, and various metadata like size and path. Folders help organize content in a logical structure. |
Files | Contains the actual documents and their metadata. Each file belongs to a folder and drive, has an owner, and includes important attributes like format, size, and path. Files represent the actual content being managed, with support for various file types and versioning through created/updated timestamps. |
Was this page helpful?