Skip to main content
GET
TypeScript

Authorizations

Authorization
string
header
required

Use a named environment API key. It starts with tr_dev_sk_, tr_prod_sk_, tr_stg_sk_, etc.

Create a named API key in the API Keys section of your Trigger.dev project dashboard. Choose the narrowest access preset that supports your integration.

Our TypeScript SDK will default to using the value of the TRIGGER_SECRET_KEY environment variable if it is set. If you are using the SDK in a different environment, you can set the key using the configure function.

Path Parameters

schedule_id
string
required

The ID of the schedule.

Response

Successful request

id
string

The unique ID of the schedule, prefixed with 'sched_'

Example:

"sched_1234"

task
string

The id of the scheduled task that will be triggered by this schedule

Example:

"my-scheduled-task"

type
string

The type of schedule, DECLARATIVE or IMPERATIVE. Declarative schedules are declared in your code by setting the cron property on a schedules.task. Imperative schedules are created in the dashboard or by using the imperative SDK functions like schedules.create().

Example:

"IMPERATIVE"

active
boolean

Whether the schedule is active or not

Example:

true

deduplicationKey
string

The deduplication key used to prevent creating duplicate schedules

Example:

"dedup_key_1234"

externalId
string

The external ID of the schedule. Can be anything that is useful to you (e.g., user ID, org ID, etc.)

Example:

"user_1234"

generator
object
timezone
string

Defaults to UTC. In IANA format, if set then it will trigger at the CRON frequency in that timezone and respect daylight savings time.

Example:

"America/New_York"

nextRun
string<date-time>

The next time the schedule will run

Example:

"2024-04-01T00:00:00Z"

environments
object[]