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

Coasty workflows API

Versioned, branching multi-step automations (DSL) and their runs.

Coasty workflows API is one of 8 APIs that Coasty publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Workflows. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 12 operations across 8 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://coasty.ai, https://coasty.ai.

12 operations 8 paths 11 schemas 1 DELETE5 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://coasty.ai
Authentication
API Key, HTTP Bearer, API Key, API Key
License
MIT
Terms of Service
Resource Areas
1

Authentication & Security 4

Coasty workflows API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (apiKey). It accepts HTTP bearer tokens (Coasty API key (sk-coasty-{live,test}-...)) (bearerAuth). An API key is passed in the header as Coasty-Signature (webhookHmac). An API key is passed in the header as X-Coasty-Signature (webhookHmacLegacy). By default, every request must be authenticated.

  • apiKey — Coasty API key. Live: sk-coasty-live-.... Sandbox: sk-coasty-test-....
  • bearerAuth — Equivalent to X-API-Key. Use whichever your client supports.
  • webhookHmac — HMAC-SHA256 credential for external schedule webhooks: t= ,v1= .
  • webhookHmacLegacy — Compatibility alias for the Coasty-Signature HMAC credential.

Paths & Operations 12

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

workflows 12

Versioned, branching multi-step automations (DSL) and their runs.

POST
/v1/workflows
Create a workflow
createWorkflow 1 param body → 200400401403404409413422
GET
/v1/workflows
List workflows
listWorkflows 1 param → 200400401403404409413422
POST
/v1/workflows/runs
Start an ad-hoc workflow run
startAdhocWorkflowRun 1 param body → 200400401402403404409413
GET
/v1/workflows/runs
List workflow runs
listWorkflowRuns 2 params → 200400401403404409413422
GET
/v1/workflows/runs/{run_id}
Get a workflow run
getWorkflowRun 1 param → 200400401403404409413422
GET
/v1/workflows/runs/{run_id}/events
Stream workflow run events (SSE)
streamWorkflowRunEvents 3 params → 200400401403404409413422
POST
/v1/workflows/runs/{run_id}/cancel
Cancel a workflow run
cancelWorkflowRun 1 param → 200400401403404409413422
POST
/v1/workflows/runs/{run_id}/resume
Approve or reject a paused workflow run
resumeWorkflowRun 1 param body → 200400401403404409413422
GET
/v1/workflows/{workflow_id}
Get a workflow
getWorkflow 1 param → 200400401403404409413422
PUT
/v1/workflows/{workflow_id}
Update a workflow
updateWorkflow 1 param body → 200400401403404409413422
DELETE
/v1/workflows/{workflow_id}
Archive a workflow
deleteWorkflow 1 param → 200400401403404409413422
POST
/v1/workflows/{workflow_id}/runs
Start a run of a saved workflow
startWorkflowRun 5 params body → 200400401402403404409413

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are WorkflowRunResponse (21 properties), WorkflowResponse (14 properties), StartWorkflowRunRequest (10 properties), WorkflowUpdateRequest (6 properties). Each schema is shown below with its type and property counts.

WorkflowResponse
object
14 properties 5 required
LlmConfig
object
Opt-in BYOK model selection. provider 'managed' (or omitting llm) keeps the platform default. There is deliberately no apikey field (422 if attempted): keys ri…
5 properties
ApiError
object
1 property 1 required
WorkflowDeleteResponse
object
4 properties 3 required
WorkflowRunResponse
object
21 properties 3 required
StartWorkflowRunRequest
object
10 properties
WorkflowCreateRequest
object
6 properties 3 required
ResumeWorkflowRunRequest
object
2 properties
ListWorkflowRunsResponse
object
4 properties 2 required
ListWorkflowsResponse
object
4 properties 2 required
WorkflowUpdateRequest
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coasty-workflows-api-openapi.yml Raw ↑

Other APIs Coasty publishes across the network.

Coasty keys API
Coasty machines API
Coasty predict API
Coasty runs API
Coasty schedules API
Coasty sessions API
Coasty triggers API
Where this information came from

This is an independent, third-party profile of Coasty workflows 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.