---
title: "Complete a waitpoint token via HTTP callback"
method: POST
path: "/api/v1/waitpoints/tokens/{waitpointId}/callback/{callbackHash}"
tags: ["waitpoints"]
---

# Complete a waitpoint token via HTTP callback

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

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`.

## Path parameters

- `waitpointId` string, required
- `callbackHash` string, required

## Request body

- object — 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`

Waitpoint token completed successfully

- CompleteWaitpointTokenResponse
  - `success` true, required — Always `true` when the request succeeds.

## Other responses

- `401` — Invalid callback URL or hash mismatch
- `404` — Waitpoint token not found
- `405` — Method not allowed
- `411` — Content-Length header is required
- `413` — Request body too large
- `500` — Internal Server Error

---

[API](https://skmtc.net/winsenlabs/apis/trigger-dev-v3-rest-api.md) · [All operations](https://skmtc.net/winsenlabs/apis/trigger-dev-v3-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/winsenlabs/trigger-dev-v3-rest-api/versions/737c498e605b/schema)