ScaiDrive

ScaiDrive is an enterprise file sync and share platform. A central server keeps the authoritative copy of every file; desktop, mobile, web, and CLI clients keep local copies in step. Teams collaborate in shared folders with NTFS-style permissions, send files to people outside the organization through password-protected links, and find content with both keyword and semantic search.

This documentation covers ScaiDrive from three perspectives — pick whichever one matches what you're trying to do.

I want to use ScaiDrive#

You're an end user. You'll sign in through your organization's SSO, browse your shares, upload and download files, share with colleagues, and create external links.

Start with the user guide. The most common paths:

• Using ScaiDrive in your browser — the web client.
• Desktop sync app — keep a local folder in step with the server.
• Mobile apps — iOS and Android.
• Sharing with your team and external sharing.

I'm running ScaiDrive#

You're a systems administrator. You'll provision tenants, manage users and groups, configure SSO, set quotas, enforce compliance policies, and integrate ScaiDrive with the rest of your infrastructure.

Start with the administration guide. The day-zero path:

1. Identity providers — connect ScaiDrive to your SSO so users can sign in.
2. Users and groups — provisioning, lifecycle, SCIM.
3. Shares and quotas — storage allocation.
4. Compliance policies — retention, DLP, legal holds.
5. SIEM integration — stream audit events to your security platform.

For deployment and ongoing ops:

• Deployment — install, scale, configure.
• Health and monitoring.
• Troubleshooting.

I'm integrating with ScaiDrive#

You're a developer building something on top of ScaiDrive — a custom client, a sync target, an AI agent, an analytics pipeline.

Start with What is ScaiDrive, then:

• Quickstart — upload your first file in five minutes.
• Authentication — get a token from ScaiKey.
• API guides — task-oriented walkthroughs of files, sharing, sync, search.
• API reference — every endpoint, every parameter, every error code.
• Core concepts — the mental model behind the API.
• Advanced topics — WebSocket events, MCP server, resumable uploads, rate limiting, enterprise compliance APIs.

The error codes reference is the right answer when something has gone wrong and you need to know what your code should do about it.

Conventions#

• Base URL. Examples use https://scaidrive.scailabs.ai. Replace with your own instance URL when self-hosting.
• API path prefix. All endpoints live under /api/v1/. Paths in this documentation include the prefix.
• Authentication. Every request (except /health and public share-link endpoints) requires a Bearer token issued by ScaiKey. See Authentication.
• Identifier prefixes. Resources have typed string IDs: usr_ users, grp_ groups, shr_ shares, fil_ files, fld_ folders, tnt_ tenants, prt_ partners. Treat them as opaque strings.
• Sizes and timestamps. Sizes are bytes (integers). Timestamps are ISO 8601 UTC (2026-04-23T10:15:00Z).
• Response shape. Successful responses return the resource directly — no {"status":"ok","data":...} envelope. Error responses are {"detail": "<message>"}. Branch on HTTP status, not on parsing the message.