Sending a test event
Open the Webhooks page
Navigate to Connections Hub and find the webhook destination you want to test.
Choose an event type
In the modal that appears, select which event type you would like to test from the dropdown. Only events that the destination is subscribed to are shown.
Understanding the result
After sending a test, you will see one of three outcomes:| Outcome | What it means |
|---|---|
| Success (2xx response) | Your endpoint received the payload and responded successfully. The integration is working. |
| Warning (non-2xx response) | The test reached your endpoint, but it returned an error (e.g. 400, 500). Check your endpoint’s logs to diagnose the issue. |
| Error (transport failure) | The request never reached your endpoint. Common causes include DNS resolution failure, connection refused, TLS certificate errors, or a request timeout. |
How test deliveries differ from production
Test payloads are nearly identical to production deliveries. The key differences are:- An
X-MentionMe-Test: trueheader is included so your system can distinguish test events from real ones. - The payload uses sample data rather than real customer data.
- Responses are captured and reported back to you in the dashboard. Production deliveries do not surface response details.
If you configured a Secret on this destination, the test payload is HMAC-signed with the same Secret. You can use a test delivery to verify your signature validation logic is working correctly.
Rate limiting
Test sends are rate-limited to 10 per minute per user per destination. If you exceed this limit, wait a moment before trying again.Troubleshooting
| Error | Suggested action |
|---|---|
| DNS resolution failed | Verify the destination URL hostname is correct and publicly resolvable. |
| Connection refused | Confirm your endpoint is running and accessible from the internet. Check firewall rules. |
| TLS error | Ensure your endpoint has a valid, non-expired SSL certificate from a trusted certificate authority. |
| Timeout | Your endpoint must respond within 10 seconds. Check for slow processing or network issues. |
| Blocked URL | The destination URL must use HTTPS and resolve to a public IP address. Private, loopback, and link-local addresses are not permitted. |
Next steps
Events
See which webhook events are available and their payload formats.
Security
Verify webhook signatures to ensure authenticity.