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

Create, list, retrieve, and complete waitpoint tokens for human-in-the-loop workflows.

Trigger.dev Waitpoints 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 Waitpoints. 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 5 operations across 5 paths, and defines 1 schema. 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.

5 operations 5 paths 1 schemas 2 GET3 POST

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 Waitpoints 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 5

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

Waitpoints 5

Create, list, retrieve, and complete waitpoint tokens for human-in-the-loop workflows.

POST
/api/v1/waitpoints
Create Waitpoint Token
createWaitpointToken body → 200
GET
/api/v1/waitpoints/{tokenId}
Retrieve Waitpoint Token
getWaitpointToken 1 param → 200
POST
/api/v1/waitpoints/{tokenId}/complete
Complete Waitpoint Token
completeWaitpointToken 1 param body → 200
GET
/api/v1/waitpoints/tokens
List Waitpoint Tokens
listWaitpointTokens 7 params → 200
POST
/api/v1/waitpoints/{tokenId}/callback
Complete Waitpoint Token via Callback
completeWaitpointTokenCallback 1 param body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is WaitpointToken (5 properties). Each schema is shown below with its type and property counts.

WaitpointToken
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trigger-dev-waitpoints-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 Schedules API
Trigger.dev Tasks API
Where this information came from

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