Skip to main content

Cloud Office

Thinkfree-managed

Open, edit, and save documents without operating your own Office server. Upload one short-lived file or connect your durable storage, then launch Word, Cell, or Show in the browser with a URL returned by Thinkfree.

Cloud Office is the Office service in Thinkfree Cloud and the Thinkfree-operated counterpart to Self-hosted Office. Thinkfree operates the document editing resources; your application controls who can request a session and which document to open.

Start here​

  1. Prepare an API Key for your backend.
  2. Upload & Edit one file to open your first document without storage setup.
  3. Connect Bring Your Own Storage when documents need to remain in their original storage.
  4. Follow the Cloud Office API guide to integrate the workflow, and use the API Reference for complete request and response fields.

Choose a workflow​

Available · No storage setup

Upload & Edit

Upload and edit one file without registering storage. After opening, save and download the document through the API before closing it.

Available · Durable storage

Bring Your Own Storage

Connect Amazon S3, S3-compatible storage, or WebDAV so Office opens and saves documents you control.

Available · Server-to-server

Cloud Office API

Review authentication and endpoints, try a request, then continue to the complete API reference.

Request and response

Cloud Office API reference

Look up request fields, response fields, link lifetimes, and error codes.

Choose the document source​

For a one-off file, upload it directly without a storage connection. For documents that must remain in Amazon S3, S3-compatible storage, or WebDAV, register a connection and identify the file by storageId and documentPath. Both workflows create a client session. Its browser group contains the URL for opening Office, and its api group contains authenticated backend endpoints. Your backend can read status, save an open Editor document, or download an open document using the API Key that created the session.

Your application also manages the user and document IDs sent with a session request. Reuse a user's userId and a document's docId across opens; different users and documents need different values. Developers returns a new clientSessionId for each successful creation request. See user, document, and session IDs for examples and the behavior when these optional fields are omitted.

Choose Bring Your Own Storage when the edited document must remain in storage that your application already owns. Your API Key can access only connections owned by the same Developer Console account, and storage credentials are never returned by the public API.

Need full infrastructure control?

Choose Self-hosted Office when Office must run inside your own network, Kubernetes cluster, or compliance boundary.