Use this file to discover all available pages before exploring further.
Send a real signed test webhook to your endpoint. Use this to verify your endpoint is reachable, responding with 2xx, and correctly validating the X-Tuco-Signature header.The test payload includes data.test: true so your handler can distinguish health checks from real events.
HMAC-SHA256 signature (same as production webhooks)
X-Tuco-Event
First event type from your subscription
X-Tuco-Timestamp
Current ISO timestamp
Test payload your endpoint receives
{ "event": "message.sent", "timestamp": "2026-04-12T12:00:00.000Z", "workspaceId": "org_xxx", "data": { "test": true, "message": "This is a health check test webhook from Tuco AI" }}
The signature is real — computed with your webhook’s secret using the same HMAC-SHA256 algorithm as production webhooks. This means your signature verification code gets tested too.
The test has a 10-second timeout. If your endpoint takes longer, it’ll report a timeout failure. Make sure your handler returns 2xx quickly and does heavy processing asynchronously.