Skip to main content
You manage webhooks per project, in the Webhooks panel on the Projects tab of the Client Dashboard. Each project has at most one webhook URL, and it receives every event type. There’s no per-type subscription. If two of your systems need the events, receive them once and fan them out yourself.

Who can do what

Organization owners and admins don’t get webhook access through their organization role. They need a project role like anyone else. Members without write access see the panel read-only. Owners and admins also receive the emails Trustware sends when a webhook event fails every attempt or the URL is disabled.

Register your webhook URL

1

Open the project

Go to the Projects tab and select the project. The Webhooks panel sits below the project’s API keys.
2

Enter the URL

Enter your endpoint in Webhook URL and click Register URL. It must be a public https URL on port 443. See webhook URL requirements for the full list. If the dashboard refuses the URL, the error says why.
3

Copy the secret

The dashboard shows your signing secret, starting with whsec_, once. Click Copy and store it in your server’s secrets. When you dismiss the alert, the secret is gone from the dashboard, and Trustware can’t show it again.
4

Send a test event

Pick an event type under Send a test event and click Send test event. The attempt appears in the delivery log, which refreshes itself until the attempt finishes.
Your URL starts receiving webhook events for changes made from this point on. It never receives events for earlier changes. Read those from /status. New URLs use API version v1.

Send a test event

A test event exercises your real handler without a real payment. You pick a type, and Trustware sends that type’s sample body to your URL through the normal delivery path, signed with your real secret. A test event differs from a real one in three ways:
  • test is true.
  • data is sample data under the route intent ID 00000000-0000-0000-0000-000000000000, which never belongs to a real route intent.
  • sequence comes from a separate per-project counter that only goes up, so your “already processed a newer sequence” check never discards a repeated test.
A test event gets one attempt, with no retries, and its failure never triggers an email or disables your URL. The one exception is 410 Gone, which disables your URL as it would for any delivery. Make sure your production handler recognizes test: true and doesn’t act on test data, such as crediting a payment. If you don’t have a server yet, a request inspector such as webhook.site can receive test events so you can see the exact request. You can send up to 10 test events a minute per project. Test events are refused while the URL is disabled.

Read the delivery log

The Delivery log, last 30 days lists every delivery attempt for the project, newest first. Click a row to see:
  • the exact request Trustware sent: method, URL, headers (including the signature), and body
  • your response status and how long it took, or the connection error
  • the first 4 KiB of your response body, shown as plain text
Each attempt also shows its outcome: While an attempt on the first page is still scheduled or sending, the log refreshes itself every few seconds. The panel also re-reads the URL’s state on each refresh, so if Trustware disables your URL while you’re watching, the panel shows it. The request in the log is byte-for-byte what was signed. If your signature check fails, compare your handler’s input with it. A different body almost always means your framework parsed or re-encoded it before you verified.

Redeliver webhook events

Redelivery sends an existing webhook event again, as one extra attempt with no retries of its own. It keeps the same webhook-id, sequence and body, and gets a fresh webhook-timestamp and signature. Your duplicate and ordering checks handle it like any other delivery.
  • Redeliver this event, in an open log row, sends that one webhook event, test events included. It’s refused while that event already has an attempt scheduled or in flight.
  • Redeliver undelivered sends every webhook event from the last 30 days that hasn’t been delivered and was recorded after you registered the URL. It skips test events and events that already have an attempt pending, and tells you how many it queued.
Both are available only while the URL is enabled. Limits per project: 30 single redeliveries a minute, and Redeliver undelivered once every 5 minutes.

Change the URL

Click Change URL to point the project at a new endpoint. The secret stays the same, and pending retries go to the new URL.

Enable and disable

Disable stops deliveries and cancels the retries that were scheduled. Webhook events are still recorded while the URL is disabled. Enable resumes delivery of new events. To catch up on what was recorded while it was disabled, use Redeliver undelivered. Trustware can also disable the URL itself. The panel shows the reason. See when your webhook URL is disabled.

Rotate the secret

Click Rotate secret to get a new secret. The dashboard shows it once, the same way as at registration. For the next 24 hours every delivery is signed with both the old and the new secret, so your server keeps verifying while you deploy the new one. After 24 hours, only the new secret signs. Rotate if you lose the secret or think it has leaked.

Delete the URL

Click Delete and type the URL’s host to confirm. Deliveries stop, pending retries are cancelled, and the secret is deleted. Webhook events keep being recorded for the project. If you register a URL again later, you get a new secret, and the new URL receives only changes made after that registration.