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 schedules API

Cron and one-shot scheduled CUA jobs.

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

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

This API exposes 11 operations across 8 paths, and defines 12 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.

11 operations 8 paths 12 schemas 1 DELETE5 GET1 PATCH4 POST

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 schedules 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 11

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

schedules 11

Cron and one-shot scheduled CUA jobs.

POST
/v1/schedules
Create a schedule
createSchedule 4 params body → 200400401402403404409413
GET
/v1/schedules
List schedules
listSchedules 1 param → 200400401403404409413422
GET
/v1/schedules/health
Schedules API health check
schedulesHealth → 200
GET
/v1/schedules/{schedule_id}
Get schedule details
getSchedule 1 param → 200400401403404409413422
PATCH
/v1/schedules/{schedule_id}
Update a schedule
updateSchedule 1 param body → 200400401403404409413422
DELETE
/v1/schedules/{schedule_id}
Delete a schedule
deleteSchedule 1 param → 200400401403404409413422
POST
/v1/schedules/{schedule_id}/pause
Pause a schedule
pauseSchedule 1 param → 200400401403404409413422
POST
/v1/schedules/{schedule_id}/resume
Resume a paused schedule
resumeSchedule 1 param → 200400401403404409413422
POST
/v1/schedules/{schedule_id}/run
Trigger a schedule run immediately
runScheduleNow 2 params body → 200400401402403404409413
GET
/v1/schedules/{schedule_id}/runs
List historical runs of a schedule
listScheduleRuns 4 params → 200400401403404409413422
GET
/v1/schedules/{schedule_id}/runs/{run_id}
Get a single run
getScheduleRun 2 params → 200400401403404409413422

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ScheduleResponse (17 properties), ScheduleCreateRequest (13 properties), ScheduleUpdateRequest (11 properties), ScheduleRunRecord (8 properties). Each schema is shown below with its type and property counts.

RunScheduleRequest
object
2 properties
HealthResponse
object
3 properties 1 required
ScheduleCreateRequest
object
13 properties 3 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
ScheduleResponse
object
17 properties 9 required
ListSchedulesResponse
object
3 properties 2 required
RunScheduleResponse
object
5 properties 5 required
ListScheduleRunsResponse
object
4 properties 2 required
ScheduleUpdateRequest
object
11 properties
ScheduleRunRecord
object
8 properties 5 required
DeleteScheduleResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

coasty-schedules-api-openapi.yml Raw ↑

Other APIs Coasty publishes across the network.

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

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