Skip to content
All product guides

API & connections / Product guide

Troubleshoot a missing webhook or channel message

Trace the event, queued delivery, receiver and Slack or Discord relay separately.

Open event endpoints

Check that the event is supported

The current endpoint selections are submission.approved, submission.rejected, payout.paid and campaign.settled. A notification preference does not add webhook event types. Confirm the actual event happened for this brand and was selected on an active endpoint.

Follow delivery in order

Test queues a delivery. A successful queue request is not proof that the receiver or final channel got it.

  1. Check endpoint activity, selected events, last status and failure count in Developers.
  2. Check whether the delivery worker ran.
  3. Inspect your receiver's request and signature-validation logs without exposing secrets.
  4. Confirm that the relay mapped the Vouched JSON into the channel's expected message format.
  5. Check the Slack or Discord response and the intended channel.

Retry without duplicating the action

Verify the signature over the timestamp and raw body before processing. Enforce a short timestamp window and deduplicate business transitions using relevant record identifiers. A receiver's 2xx only proves acceptance there; it does not prove a downstream message was displayed. Share route, time and status in support requests, never the secret or full private payload.

Common questions

Can I paste a Discord webhook directly into Vouched?

No. Vouched emits its own event JSON. Use a receiver that verifies the request and relays a correctly formatted message to Discord or Slack.

Need a hand?

Use Feedback in your dashboard if a guide does not answer your question. Include the page, what you expected and what happened. Never include a password, API key, account number or private payload.

Open API & connections
Need help