Overview

CCS Files API 1.0

REST API of files.centralcodestation.com: storage, folders, uploads, previews, search, permissions, shares and audit for tenant applications. Every route is under /api/v1; routes are kebab-case and every field is snake_case.

Authentication: a bearer access token issued by the CCS Identity Server for the Files API resource (aud = files-api).

User tokens need the files:access scope. A token issued to a tenant application’s own client works only in that application; a client of a platform application works in any tenant the user belongs to, in a tenant application that has not switched Files off, or in its own platform application.
Machine tokens (client_credentials) need files:manage (full control of the application’s storage), files:read (reads and download URLs) or files:config.manage (settings, usage, webhooks). A machine client of a tenant application works only in its own tenant and application.

File bytes never pass through the API: uploads go to signed URLs from an upload ticket, downloads and previews are short-lived signed URLs.

Errors are { status_code, error, message, path, timestamp }; error is a stable snake_case code. Lists page with ?after=<next_cursor>&limit=.

Information