Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Kin Lane

Chat with Kin

AI assistant · trained on my blog

Terminal Use

Terminal Use Filesystems API

The Filesystems API from Terminal Use — 9 operation(s) for filesystems.

Documentation Provider Profile APIs.io OpenAPI GitHub

Terminal Use Filesystems API is one of 28 APIs that Terminal Use publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Filesystems. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 9 paths, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against the base URL https://api.terminaluse.com.

10 operations 9 paths 14 schemas 5 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.terminaluse.com
Resource Areas
1

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 5 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Filesystems 10
GET
/filesystems
List Filesystems
filesystems_list 1 param → 200422
POST
/filesystems
Create Filesystem
filesystems_create body → 201422
GET
/filesystems/{filesystem_id}
Get Filesystem
filesystems_retrieve 1 param → 200422
POST
/filesystems/{filesystem_id}/download-url
Get Download URL
filesystems_get_download_url 1 param body → 200422
GET
/filesystems/{filesystem_id}/file-download
Download File
filesystems_download_file 2 params → 200422
PUT
/filesystems/{filesystem_id}/file-upload
Upload File
filesystems_upload_file 8 params body → 200201400404409412422428
GET
/filesystems/{filesystem_id}/files
List Files
filesystems_list_files 7 params → 200422
GET
/filesystems/{filesystem_id}/files/{file_path}
Get File
filesystems_get_file 3 params → 200422
POST
/filesystems/{filesystem_id}/sync-complete
Complete Sync Operation
filesystems_sync_complete 1 param body → 200422
POST
/filesystems/{filesystem_id}/upload-url
Get Upload URL
filesystems_get_upload_url 1 param body → 200422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are FilesystemResponse (11 properties), FilesystemFileResponse (10 properties), FilesystemFile (9 properties), SingleFileUploadResponse (7 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
PresignedUrlResponse
object
Response model for presigned URL operations.
5 properties 4 required
FilesystemFile
object
File metadata - used for both input (sync-complete) and as base for response.
9 properties 2 required
ListFilesResponse
object
Response model for listing files in a filesystem.
4 properties 3 required
ValidationError
object
3 properties 3 required
FileUploadWriteMode
string
Single-file upload write semantics.
FilesystemFileResponse
object
File metadata response - adds server-side fields.
10 properties 3 required
FilesystemStatus
string
Filesystem lifecycle status states.
PresignedUrlRequest
object
Request model for presigned URL generation.
1 property
FilesystemCreate
object
Request model for creating a filesystem. Filesystems inherit permissions from their parent project.
2 properties 1 required
SyncCompleteResponse
object
Response model for sync-complete operation.
4 properties 4 required
SingleFileUploadResponse
object
Response model for single-file upload operations.
7 properties 7 required
FilesystemResponse
object
Response model for filesystem operations.
11 properties 3 required
SyncCompleteRequest
object
Request model for completing a sync operation.
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

terminal-use-filesystems-api-openapi.yml Raw ↑

Other APIs Terminal Use publishes across the network.

Terminal Use Agent APIKeys API
AE Profile APIs.io
Terminal Use Agent Task Tracker API
AE Profile APIs.io
Terminal Use Agents API
AE Profile APIs.io
Terminal Use API Keys API
AE Profile APIs.io
Terminal Use Authentication API
AE Profile APIs.io
Terminal Use Branch Events API
AE Profile APIs.io
Terminal Use Branches API
AE Profile APIs.io
Terminal Use Builds API
AE Profile APIs.io
Terminal Use CLI Authentication API
AE Profile APIs.io
Terminal Use Environments API
AE Profile APIs.io
Terminal Use Events API
AE Profile APIs.io
Terminal Use Groups API
AE Profile APIs.io
#Filesystems
← Back to T APIs
API Details
ID
terminal-use:terminal-use-filesystems-api
Base URL
https://api.terminaluse.com
Docs
https://docs.terminaluse.com
Provider
Terminal Use
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network