Skip to content
AveraAveraAvera Documentation

Overview

Files & Drive 1.0.0

Section titled “Files & Drive 1.0.0”

The files & Drive surface of the Avera REST API: Files · Avera Drive.

Information

  • License: Proprietary
  • OpenAPI version: 3.1.0

Files

Section titled “Files”
POST
/api/v1/files/upload-complete
GET
/api/v1/files/{fileContentId}/download-local
POST
/api/v1/files/upload-url
GET
/api/v1/files/{fileContentId}
GET
/api/v1/files/{fileContentId}/download-url
GET
/api/v1/files/quota
POST
/api/v1/files/upload-local/{uploadId}

Avera Drive

Section titled “Avera Drive”
GET
/api/v1/drive/account
POST
/api/v1/drive/changes
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/nodes/{nodeId}/children
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/nodes/{nodeId}/content
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/nodes/{nodeId}/link
GET
/api/v1/drive/projects
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/nodes/{nodeId}
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/nodes/{nodeId}/path
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/resolve
GET
/api/v1/drive/projects/{projectId}/branches/{branchKey}/root

Authentication

Section titled “Authentication”

bearerAuth

Section titled “bearerAuth”

Every request carries a bearer token: the session token issued at sign-in, or an OAuth 2.1 access token from a connector grant. HTTP basic is disabled (see SecurityConfig), and the requirement is declared once here rather than on each operation, since it is the same for the whole API.

Security scheme type: http

Bearer format: JWT