How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Terminal Use Tasks API

The Tasks API from Terminal Use — 14 operation(s) for tasks.

Terminal Use Tasks 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 Task. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 19 operations across 14 paths, and defines 52 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.terminaluse.com.

19 operations 14 paths 52 schemas 2 DELETE7 GET8 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 19

Across 14 paths, the API surfaces 19 operations — 2 DELETE, 7 GET, 8 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Tasks 19
GET
/tasks
List Tasks
tasks_list 13 params → 200422
POST
/tasks
Create Task
tasks_create body → 201422
POST
/tasks/migrate
Migrate Tasks Between Versions
tasks_migrate body → 200422
DELETE
/tasks/name/{task_name}
Delete Task by Name
tasks_delete_by_name 2 params → 200422
GET
/tasks/name/{task_name}
Get Task by Name
tasks_retrieve_by_name 3 params → 200422
PUT
/tasks/name/{task_name}
Update Task by Name
tasks_update_by_name 2 params body → 200422
GET
/tasks/name/{task_name}/stream
Stream Task Events by Name
tasks_stream_by_name 2 params → 200422
DELETE
/tasks/{task_id}
Delete Task by ID
tasks_delete 1 param → 200422
GET
/tasks/{task_id}
Get Task by ID
tasks_retrieve 2 params → 200422
PUT
/tasks/{task_id}
Update Task by ID
tasks_update 1 param body → 200422
POST
/tasks/{task_id}/cancel
Cancel Task
tasks_cancel 1 param → 200422
POST
/tasks/{task_id}/events
Send Event to Task
tasks_send_event 1 param body → 201422
POST
/tasks/{task_id}/handler-end
Handler End
tasks_handler_end 1 param body → 200422
GET
/tasks/{task_id}/stream
Stream Task Events by ID
tasks_stream 1 param → 200422
GET
/tasks/{task_id}/system-folder-types
List System Folder Types
tasks_list_system_folder_types 1 param → 200422
GET
/tasks/{task_id}/system-folders/{folder_type}
Get System Folder
tasks_get_system_folder 2 params → 200422
POST
/tasks/{task_id}/system-folders/{folder_type}/download-url
Get System Folder Download URL
tasks_get_system_folder_download_url 2 params body → 200422
POST
/tasks/{task_id}/system-folders/{folder_type}/sync-complete
Complete System Folder Sync
tasks_system_folder_sync_complete 2 params body → 200422
POST
/tasks/{task_id}/system-folders/{folder_type}/upload-url
Get System Folder Upload URL
tasks_get_system_folder_upload_url 2 params body → 200422

Schemas 52

The contract defines 52 schemas that model the data the API accepts and returns. The most detailed are VersionResponse (24 properties), TaskResponse (13 properties), Task (12 properties), Agent (11 properties). Each schema is shown below with its type and property counts.

UpdateTaskRequest
object
1 property
PresignedUrlRequest
object
Request model for presigned URL generation.
1 property
TextDeltaPart
object
Incremental text content.
4 properties 2 required
ValidationError
object
3 properties 3 required
StreamMetadata
object
Extended metadata for finish events.
5 properties
VersionStatus
string
Status of a version in its lifecycle.
TaskResponse
object
Task response model with optional related data based on relationships
13 properties 3 required
StartPart
object
Marks the start of a streaming session.
1 property
TextStreamPartWrapper
Wrapper for TextStreamPart union for proper serialization.
StreamUsage
object
Token usage for streaming events.
3 properties 2 required
SystemFolderSyncCompleteResponse
object
Response model for system folder sync-complete operation.
4 properties 4 required
MigrateTasksResponse
object
Response model for task migration operation.
4 properties 3 required
ToolInputStartPart
object
Marks the start of tool input streaming.
4 properties 2 required
TextStartPart
object
Marks the start of a text block.
3 properties 1 required
DataPart
object
Generic data part for unknown/passthrough content.
2 properties 1 required
HTTPValidationError
object
1 property
HandlerCompletePart
object
Marks completion of event/send handler lifecycle for a specific event.
6 properties 3 required
HandlerEndResponse
object
2 properties 2 required
Task
object
12 properties 3 required
TaskRelationships
string
Task relationships that can be loaded
ToolInputDeltaPart
object
Incremental tool input JSON.
4 properties 2 required
PresignedUrlResponse
object
Response model for presigned URL operations.
5 properties 4 required
SDKType
string
SDK type for agent runtime.
StartStepPart
object
Marks the start of a new step (API call).
4 properties
CreateTaskRequest
object
Request for POST /tasks
7 properties
Event
object
Event returned from the events API. Content is TextPart or DataPart (human-readable content only).
7 properties 4 required
TextEndPart
object
Marks the end of a text block.
3 properties 1 required
FinishPart
object
Marks the end of the entire streaming session.
4 properties 2 required
ACPType
string
Type of ACP server.
DeleteResponse
object
2 properties 2 required
SystemFolderSyncCompleteRequest
object
Request model for completing a system folder sync operation.
5 properties 3 required
TextPart
object
Text content part.
2 properties 1 required
Agent
object
11 properties 6 required
SystemFolderType
string
Enumeration of system folder types that can be synced per-task.
ReasoningStartPart
object
Marks the start of a reasoning block.
3 properties 1 required
AgentStatus
string
Agent status - runtime statuses (Ready/Failed/Unhealthy) now live on Deployment.
ReasoningDeltaPart
object
Incremental reasoning content.
4 properties 2 required
SystemFolderResponse
object
Response model for a task's system folder record.
9 properties 3 required
FinishReason
string
Reason for stream completion.
ReasoningEndPart
object
Marks the end of a reasoning block.
3 properties 1 required
HandlerEndRequest
object
5 properties
ToolResultPart
object
Tool execution result.
5 properties 3 required
FinishStepPart
object
Marks the end of a step (API call).
4 properties 2 required
VersionResponse
object
Full version details.
24 properties 11 required
ToolInputEndPart
object
Marks the end of tool input streaming.
3 properties 1 required
ToolCallPart
object
Complete tool call with parsed input.
5 properties 3 required
CreateTaskEventRequest
object
Request for POST /tasks/{taskid}/events Content accepts TextPart or DataPart only. Other message types (tool calls, reasoning, etc.) are agent-generated and se…
3 properties
SystemFolderTypeResponse
object
Response model for a system folder type from the registry.
3 properties 3 required
AgentInputType
string
MigrateTasksRequest
object
Request model for migrating tasks between versions.
4 properties
StreamErrorPart
object
Error during streaming.
3 properties 1 required
TaskStatus
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Terminal Use publishes across the network.

Terminal Use Agent APIKeys API
Terminal Use Agent Task Tracker API
Terminal Use Agents API
Terminal Use API Keys API
Terminal Use Authentication API
Terminal Use Branch Events API
Terminal Use Branches API
Terminal Use Builds API
Terminal Use CLI Authentication API
Terminal Use Environments API
Terminal Use Events API
Terminal Use Filesystems API
Where this information came from

This is an independent, third-party profile of Terminal Use Tasks API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.