Statuses & error codes
Below is a reference of Hookdeck's internal event statuses and error codes, as well as some common HTTP status codes.
Hookdeck event status
| Event Status | Description |
|---|---|
| Pending | The event is pending delivery |
| Failed | The most recent delivery attempt received an HTTP status code in the failure range |
| Successful | The most recent delivery attempt received an HTTP status code in the success range |
| On hold | Delivery will be attempted when the associated connection is unpaused |
Hookdeck error codes
If your destination was unreachable or failed to respond, the event will appear in the dashboard with an ERR flag. A more specific error code can be found by inspecting the event.
| Hookdeck Error Code | Explanation |
|---|---|
| CONNECTION_REFUSED | The request to your destination could not be made because the connection was refused. |
| CONNECTION_RESET | The request to your destination could not be made because the connection was forcibly closed by your server. |
| NOT_FOUND | The request to your destination could not be made because the domain or host was not found or unavailable. |
| TIMEOUT | The request to your destination exceeded the 60-second timeout window. The request might have still been processed by your destination. |
| MISSING_URL | Your destination does not have a HTTP URL configured. It can only receive attempts on the CLI. |
| CLI | The attempt failed to be forwarded to your local server by the CLI. Check your console for more details. |
| SELF_SIGNED_CERT | Your destination uses a self-signed SSL certificate. Hookdeck only supports valid, verifiable certificates. |
| ERR_TLS_CERT_ALTNAME_INVALID | Your destination's SSL certificate is not valid. |
| SSL_CERT_EXPIRED | Your destination's SSL certificate is expired. |
| SSL_ERROR_CA_UNKNOWN | The intermediate certificate / CA Bundle is invalid or mismatched. |
| UNKNOWN | An uncategorized error occurred. If one of these errors is triggered, Hookdeck's technical team is notified and will investigate. |
HTTP response status codes
When your destination responds with a valid HTTP response code, it will be displayed as the event's status. A response code between 200 and 299 is considered successful. A response code of 400 or above is considered a failure.
| Status Code | Description | Explanation |
|---|---|---|
| 200 | Good Request | Your request is valid. |
| 400 | Bad Request | Your request is invalid and could not be understood. |
| 401 | Unauthorized | Your API key is wrong. |
| 403 | Forbidden | Access to the requested resource is restricted. |
| 404 | Not Found | The resource could not be found. |
| 413 | Payload Too Large | The payload size exceeds the limit. |
| 422 | Unprocessable Entry | The request was understood but contains invalid input. |
| 429 | Too Many Requests | The request limit for a specific time period has been exceeded. |
| 500 | Internal Server Error | There was a problem with the server. Try again later. |
| 503 | Service Unavailable | The server is temporarily offline for maintenance. Try again later. |