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

Trigger.dev Schedules API

Create and manage cron schedules with IANA timezone support.

Trigger.dev Schedules API is one of 10 APIs that Trigger.dev publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 4 JSON Schema definitions.

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

This API exposes 8 operations across 5 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 3.1.0.

Requests are made against 2 base URLs: https://api.trigger.dev, https://your-self-hosted-instance.com.

8 operations 5 paths 3 schemas 1 DELETE3 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.1.0
Base URL
https://api.trigger.dev
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

Trigger.dev Schedules API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Secret API key (starts with trdev, trprod, or trstg). Set TRIGGERSECRETKEY environment variable or pass in Authorization header.

Paths & Operations 8

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

Schedules 8

Create and manage cron schedules with IANA timezone support.

GET
/api/v1/schedules
List Schedules
listSchedules → 200
POST
/api/v1/schedules
Create Schedule
createSchedule body → 200400
GET
/api/v1/schedules/{scheduleId}
Retrieve Schedule
getScheduleById 1 param → 200
PUT
/api/v1/schedules/{scheduleId}
Update Schedule
updateSchedule 1 param body → 200
DELETE
/api/v1/schedules/{scheduleId}
Delete Schedule
deleteSchedule 1 param → 200
POST
/api/v1/schedules/{scheduleId}/activate
Activate Schedule
activateSchedule 1 param → 200
POST
/api/v1/schedules/{scheduleId}/deactivate
Deactivate Schedule
deactivateSchedule 1 param → 200
GET
/api/v1/schedules/timezones
Get Timezones
getTimezones → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Schedule (10 properties), CreateScheduleRequest (5 properties), UpdateScheduleRequest (3 properties). Each schema is shown below with its type and property counts.

CreateScheduleRequest
object
5 properties 3 required
UpdateScheduleRequest
object
3 properties
Schedule
object
10 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trigger-dev-schedules-api-openapi.yml Raw ↑

Other APIs Trigger.dev publishes across the network.

Trigger.dev Realtime API
Trigger.dev Batches API
Trigger.dev Deployments API
Trigger.dev Environment Variables API
Trigger.dev Query API
Trigger.dev Queues API
Trigger.dev Runs API
Trigger.dev Tasks API
Trigger.dev Waitpoints API
Where this information came from

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