Testing & Deliveries
Sending a test event
Section titled “Sending a test event”Click Test next to any webhook to send a test delivery. Tolinku sends a POST request to your URL with a test event type:
{ "event": "test", "timestamp": "2026-03-02T14:00:00.000Z", "data": { "webhook_id": "wh_abc123", "appspace_id": "as_def456" }}The test includes a valid X-Webhook-Signature header, so you can verify your signature validation logic. The dashboard shows the HTTP status code returned by your server.
Delivery logs
Section titled “Delivery logs”Each webhook keeps a log of the last 50 deliveries. Click on a webhook to view its delivery history.
Each log entry shows:
| Field | Description |
|---|---|
| Event type | The event that triggered the delivery |
| Timestamp | When the delivery was sent |
| Status code | The HTTP response code from your server |
| Response time | How long your server took to respond (milliseconds) |
| Success | Whether the delivery was accepted (2xx) or failed |
| Attempt | Which attempt this was (1, 2, or 3) |
| Error | Error message if the delivery failed |
Retry behavior
Section titled “Retry behavior”If your server does not respond with a 2xx status code (or does not respond within 10 seconds), Tolinku retries the delivery automatically:
| Attempt | Delay |
|---|---|
| 1st retry | 1 minute |
| 2nd retry | 5 minutes |
| 3rd retry | 30 minutes |
After 3 failed attempts, the delivery is marked as failed and no further retries are attempted. Each retry attempt appears as a separate entry in the delivery log.
Troubleshooting
Section titled “Troubleshooting”Deliveries failing with 401/403: Your server is rejecting the request. Check that your signature verification uses the correct signing secret and processes the raw request body.
Deliveries failing with timeout: Your server is not responding within 10 seconds. Webhook handlers should process quickly and return 200 immediately. If you need to do heavy work, acknowledge the webhook first, then process asynchronously.
No deliveries showing: Check that the webhook is active and subscribed to the correct event types. Also verify that the events are actually occurring (e.g. links are being clicked).