Managing Webhooks

After creating your webhooks, you can monitor their activity, view event details, and manage their configuration through the Trust portal.

Managing existing webhooks

Viewing webhook configuration

In the webhooks list, each webhook displays:

• Payload URL: The endpoint where webhooks are sent

• Status: Whether the webhook is Active or Inactive

• Actions: Options to view events, edit, or delete the webhook

To access webhook events, click the View events button for any webhook.

Viewing webhook events

Webhook events list

After clicking View events from the webhook management page, you can see all recent webhook deliveries for that specific webhook:

The webhook events page displays:

• Event ID: Unique identifier for each webhook delivery attempt

• Event Type: The type of event that triggered the webhook (e.g., COMMUNICATION.COMMUNICATIONCREATEDEVENT)

• Date: When the webhook was sent

• Status: Visual indicator showing successful (✓) or failed (✗) delivery

• Event details: Link to view detailed information about the webhook delivery

Event details

Click on Event details for any webhook delivery to see comprehensive information:

The event details page shows:

Request Tab

• Payload: The complete JSON payload that was sent to your webhook endpoint

• Headers: HTTP headers included in the webhook request

Responses Tab

• Response Status: HTTP status code returned by your endpoint

• Response Headers: Headers returned by your webhook endpoint

• Response Body: The response body from your endpoint

You can use the Resend button to retry failed webhook deliveries. Note that the Resend button is only available for webhooks that failed (marked with ✗).

Understanding webhook delivery status

• ✓ Green checkmark: Webhook was successfully delivered (HTTP 2xx response)

• ✗ Red X: Webhook delivery failed (non-2xx response, timeout, or connection error)

Redelivering failed webhooks

For failed webhook deliveries (marked with ✗), you can manually retry the delivery:

1. Click on Event details for the failed webhook

2. Review the failure reason in the Responses tab

3. Click the Resend button to retry the delivery

4. The webhook will be sent again with the same payload and headers

Editing webhooks

Click the "Edit" button to modify webhook settings:

You can update:

• Payload URL: Change the destination endpoint

• Secret: Update the webhook signature secret

• Authentication type: Modify authentication method (None, Basic, API Key)

• Event selection: Change which events trigger the webhook

• Active status: Enable or disable the webhook

Troubleshooting failed webhooks

When webhooks fail (marked with ✗), check the event details to understand why:

1. 4xx Errors: Usually indicate issues with your endpoint

   • 404: Webhook URL not found

   • 401/403: Authentication issues

   • 400: Your endpoint rejected the payload format

2. 5xx Errors: Server errors on your endpoint

   • 500: Internal server error in your webhook handler

   • 502/503: Your server is unavailable

3. Timeout: Your endpoint took too long to respond (> 2 seconds)

Best practices for webhook management

Next steps

• Learn about webhook events to understand payload structures

• Implement signature verification for security

• Follow best practices for reliable webhook handling