Status notifications
Your application can receive render-status notifications instead of repeatedly polling. Keep the render ID and status lookup as a way to reconcile results.
1. Prepare a receiver
Use a publicly reachable HTTPS endpoint, not localhost/private networking. Verify signatures; a plausible-looking body is not proof of origin.
2. Create an endpoint in the app
Open project Webhooks, supply a name and URL, then save the signing secret securely on your backend. The secret is revealed at creation; keep it out of frontend code and screenshots.
3. Send a test
Use Test and inspect delivery HTTP status, attempts and errors. A webhook.test event is not a completed PDF.
4. Handle render events
Real notifications use renders.status. Persist receipt safely and respond promptly, then perform longer processing separately. Do not acknowledge before your system can reliably retain the event.
Operate the endpoint
Enable/disable deliberately and use delivery history for diagnosis. Fix an existing endpoint rather than creating duplicates. Read signature verification before processing real data.