Authentication
Use API credentials or tokens appropriate for the integration scope and environment.
Developers
Developer surfaces should feel direct: authenticate, move files, manage sharing, collect submissions, and connect BeDrive to the systems where work already happens.
A familiar API shape for file, folder, sharing, and workspace actions
Credential-based access for server-side integrations and automation
A foundation for activity, progress, and automation around file work
Start
The API page should help technical teams understand what kind of integrations BeDrive is meant to support without pretending every SDK is already public.
Use API credentials or tokens appropriate for the integration scope and environment.
Build workflows that create, read, move, rename, upload, download, and organize work.
Create controlled handoffs and intake flows around links and file request workflows.
Example flow
Teams often need more than storage: a client upload starts a review, a finished file triggers delivery, or a shared folder becomes part of a project pipeline.
Developer support
If you are building against BeDrive for a product, internal tool, migration, or client workflow, we can help route the request and confirm what is available.
Contact developers@bedrive.io with the use case, expected volume, and the parts of BeDrive you need to connect.
Public SDK availability should be listed only when packages are published and maintained. Until then, this page should describe supported API patterns without inventing package names.
For production integrations, include authentication requirements, data scope, and whether the integration acts on behalf of a user or a workspace.
The best API conversations start with the workflow, not the endpoint list.