Webhook Delivery Logs
Inspect NOCK webhook delivery attempts, failures, retries, and final delivery states.
NOCK records webhook delivery attempts so you can debug downstream integrations without guessing whether an event was sent.
Delivery states
| Status | Meaning |
|---|---|
pending | Delivery is queued and has not been attempted yet. |
processing | Delivery has been claimed for retry processing. |
delivered | Endpoint returned a successful 2xx response. |
failed | Endpoint failed, but the delivery can still be retried. |
exhausted | Maximum retry attempts were used. |
abandoned | Endpoint or payload became unavailable before retry. |
NOCK stores response status, a bounded response body excerpt, error text, attempt count, and retry timestamps.
Retries and retention
- Webhook deliveries are attempted immediately after they are queued.
- Failed ticket-event deliveries are retried by the internal retry job.
- Ticket-event deliveries have up to 3 automatic attempts.
- Workspace admins can retry failed or exhausted deliveries manually from workspace integrations.
- Manual retries of exhausted deliveries atomically extend that delivery by one attempt so attempt counts stay readable, for example
4/4instead of4/3. webhook.testdeliveries are one-attempt manual checks and are not automatically retried by the internal retry job.- Finalized delivery logs are cleaned up after the retention window.
Query delivery logs
API keys need webhooks:write.
curl -sS "https://nocknock.cloud/api/v1/webhook-deliveries?status=failed&limit=25" \
-H "Authorization: Bearer $NOCK_API_KEY"Supported filters:
| Query parameter | Description |
|---|---|
endpoint_id | Return deliveries for one webhook endpoint. |
project_id | Return deliveries for one project. |
ticket_id | Return deliveries for one ticket. |
status | Return deliveries with one status. |
limit | 1 to 100, default 25. |
Delivery payload bodies are not returned through this endpoint. Use the event ID, ticket ID, status, and error fields for troubleshooting.
Dashboard view
Workspace admins can also inspect recent webhook deliveries from workspace integrations. Use this when a no-code tool or external endpoint is failing and you need to see whether NOCK is receiving 2xx responses. The dashboard can send a signed webhook.test delivery for endpoint verification and can retry failed or exhausted deliveries without waiting for the retry job. Manual test and retry actions are rate limited to avoid accidental endpoint floods.