SHIVA REDDY VANJA
4dc504d9d0
Fixed documentation examples to use correct 'data' field instead of 'output' for the waitpoint token completion endpoint. The API schema expects 'data' in the request body, but all code examples (curl, Python, Ruby, Go) incorrectly showed 'output', causing waitpoints to complete with empty/undefined output when users followed the docs. Fixes #2872 Closes #<issue> ## ✅ Checklist - [x] I have followed every step in the [contributing guide](https://github.com/triggerdotdev/trigger.dev/blob/main/CONTRIBUTING.md) - [x] The PR title follows the convention. - [x] I ran and tested the code works --- ## Testing _[Describe the steps you took to test this change]_ This is simple doc fix --- ## Changelog _[Short description of what has changed]_ Documentation example for the specific api route had a wrong field, fixed that to have correct field --- ## Screenshots _[Screenshots]_ <img width="780" height="252" alt="Screenshot 2026-01-14 at 10 49 50 PM" src="https://github.com/user-attachments/assets/50a03f2c-edfb-4bd4-bb72-a0fd79e77216" /> The above image shows the correct request format, but docs previously had incorrect payload. <img width="723" height="307" alt="Screenshot 2026-01-14 at 11 24 01 PM" src="https://github.com/user-attachments/assets/b9096225-3f7c-4511-b8c2-e8144c896900" /> This is the exact wrong field in docs, that was fixed https://trigger.dev/docs/wait-for-token#from-another-language 💯 Co-authored-by: appdevelopers9a <appdeveloper@s9alabs.com>
Development
Install and initial setup
pnpm install
Running the app
pnpm run dev --filter docs
View the app locally
It runs locally here:
http://localhost:3050