Remberg files API is one of 19 APIs that Remberg publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include files. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes
9 operations
across 6 paths,
and defines 5 schemas.
It is described by OpenAPI 3.0.0, at version v1.
Requests are made against a single base URL, https://api.remberg.de.
9 operations6 paths5 schemas1 DELETE4 GET2 PATCH2 POST
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.0.0
API Version
v1
Base URL
https://api.remberg.de
Authentication
API Key
Resource Areas
1
Authentication & Security 1
Remberg files API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as authorization (authorization).
Paths & Operations 9
Across 6 paths, the API surfaces 9 operations — 1 DELETE, 4 GET, 2 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.
files 9
GET
/v1/files
Returns a list of top-level files and folders. Use the folderId query parameter to retrieve nested resources.
/v1/files_get11 params→ 200400403
POST
/v1/files
Upload one or more files using multipart/form-data. Optionally specify a target folder via the metadata payload.
/v1/files_postbody→ 201400403409
GET
/v1/files/resolve
Resolve a file or folder by its slash-delimited path (e.g. "Engineering/Specs/vacuum.pdf") and return its metadata.
/v1/files/resolve_get1 param→ 200400403404
GET
/v1/files/{id}
Retrieve the metadata of a single file or folder by its unique identifier.
/v1/files/{id}_get1 param→ 200400403404
PATCH
/v1/files/{id}
Update the metadata of a file or folder by its unique identifier.
/v1/files/{id}_patch1 parambody→ 200400403404409
DELETE
/v1/files/{id}
Delete a file or folder by its unique identifier. This is a cascading operation — all nested child items will also be permanently deleted.
/v1/files/{id}_delete1 param→ 204400403404
GET
/v1/files/{id}/download
Download the binary content of a file by its unique id.
/v1/files/{id}/download_get1 param→ 200400403404
POST
/v1/files/folder
Create a new folder. Optionally specify a parent folder to create a nested folder.
/v1/files/folder_postbody→ 201400403409
PATCH
/v1/files/{id}/content
Replace the binary content of an existing file by its unique id.
The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are DriveFilesCfaResponseDto (16 properties), DriveFilesCfaUpdateOneBodyDto (10 properties), DriveFilesCfaCreateFileMultipartBodyDto (9 properties), DriveFilesCfaCreateFolderBodyDto (8 properties). Each schema is shown below with its type and property counts.
DriveFilesCfaResponseDto
object
16 properties8 required
DriveFilesCfaFindManyResponseDto
object
1 property1 required
DriveFilesCfaCreateFileMultipartBodyDto
object
9 properties1 required
DriveFilesCfaCreateFolderBodyDto
object
8 properties1 required
DriveFilesCfaUpdateOneBodyDto
object
10 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
