Complete a waitpoint token via HTTP callback

Completes a waitpoint token using the pre-signed callback URL returned in the url field when the token was created. No API key is required — the callbackHash in the URL acts as the authentication token.

This is designed to be given directly to external services (e.g. as a webhook URL) so they can unblock a waiting run without needing access to your API key. The entire request body is passed as the output data to the waiting run.

If the token is already completed, this is a no-op and returns success: true.

POST /api/v1/waitpoints/tokens/{waitpointId}/callback/{callbackHash}

cURL

cURL

# The full URL is returned as `url` when you create a token
curl -X POST "https://api.trigger.dev/api/v1/waitpoints/tokens/waitpoint_abc123/callback/abc123hash" \
  -H "Content-Type: application/json" \
  -d '{"status": "approved", "comment": "Looks good to me!"}'

200

{
  "success": true
}

Path Parameters

waitpointId · string · required

The ID of the waitpoint token.

callbackHash · string · required

The HMAC hash that authenticates the request. This is embedded in the url returned when creating the token — do not construct it manually.

Body

application/json

Any JSON object. The entire body is passed as the output data to the run waiting on this token. If the body is not valid JSON, an empty object is used.

Response

200

application/json

Waitpoint token completed successfully

success · enum<boolean> · required

Always true when the request succeeds.

Available options: true