> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mention-me.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Test a Webhook

> Send a test event to your webhook destination to verify your integration is working correctly.

Before going live with a webhook integration, you can send a test event from the Mention Me dashboard to verify your endpoint receives and processes webhook payloads correctly.

Test deliveries use the same HTTP client, headers, HMAC signing, and timeout as production deliveries, so a successful test confirms your integration will work in production.

## Sending a Test Event

<Steps>
  <Step title="Open the Webhooks page">
    Navigate to **Connections Hub** and find the webhook destination you want to test.
  </Step>

  <Step title="Open the actions menu">
    Click the **⋮** menu on the webhook destination row, then choose **Send test**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Send the test">
    Click **Send test**. Mention Me will send a sample payload to the destination URL and report the result.
  </Step>
</Steps>

## 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: true` header 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.

<Info>
  If you configured a [Secret](/api-reference/webhooks/security) 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.
</Info>

## 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

<CardGroup cols={2}>
  <Card title="Events" icon="bell" href="/api-reference/webhooks/events">
    See which webhook events are available and their payload formats.
  </Card>

  <Card title="Security" icon="shield-check" href="/api-reference/webhooks/security">
    Verify webhook signatures to ensure authenticity.
  </Card>
</CardGroup>