Introduction

The SecureCloud API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

What's new in version 13.0

Most endpoints work exactly as before. Please check your integration if you use one of the following:

• File comments are now addressed by the file's unique ID (file_uuid) instead of its path: /api/v2.1/repos/{repo_id}/file/{file_uuid}/comments/. Comments now support replies. The previous endpoints under /api2/repos/{repo_id}/file/comments/ have been removed.
• Contents of a shared folder link are listed via /api/v2.1/share-links/{token}/dirents/. The previous endpoint /api2/d/{token}/dir/ has been removed.
• Revoking an invitation uses POST /api/v2.1/invitations/{token}/revoke/.
• Transferring a library keeps existing shares only if you send reshare=true.
• Share links support restricting access to specific users or email addresses (user_scope).
• New endpoints for library API tokens: recently changed and recently deleted files.

The complete list, including corrections to the previous documentation, is available on the page API changes in SecureCloud 13.0.

Terminology

Users

• user_id: The unique user id in the form [email protected]. It is unchangeable. The user's real email address is stored in the contact_email field.
• email: Same as user_id. The term is still used in API's returned value. The term should be avoided in other places.
• username: Same as user_id, used internally.
• contact_email: User's contact email, which is also a user's real email. It is changeable.

Usage

Authentication & Status Codes

For detailed information on authentication methods and HTTP status codes, please refer to our dedicated support articles on Authentication and Status Codes.

Actions: User vs. Administrator

The API clearly distinguishes between two areas:

User actions include managing files, folders, and libraries, as well as sharing resources and personal settings.

Administrator actions include system-wide operations such as managing user accounts, groups, organizations, share links, notifications, and logs. These endpoints are marked with "System Admin" in the documentation.

API Documentation Features

Our API documentation offers the following helpful features:

Interactive API testing: You can execute API calls directly in your browser without having to install additional tools. Simply enter your authentication credentials and test the endpoints live.

Code snippets: Code examples in various programming languages are automatically generated for each API endpoint, including cURL, Python, JavaScript, PHP, Ruby, and more. This allows you to copy the appropriate code directly into your project.

Detailed request/response documentation: Each endpoint shows you exactly which parameters are expected and how the response is structured – including sample data.

Server selection: You can select your desired server in the documentation if you operate your own SecureCloud instance with a custom domain.

Getting Started

To use the API, we recommend the following approach:

1. Open the API documentation
2. Start with the "Ping server" endpoint at /api2/ping/ – this requires no authentication and returns a pong in case your URL is right
3. Generate an account token via the corresponding authentication endpoint /api2/auth-token/
4. Explore the other endpoints according to your requirements, using the previously generated account token

Help and Support

If you have questions about using the API, you can reach us at:

• ☎️ +49 (0) 9181 - 27 308 -0
• 📧 [email protected]