Skip to main content

Webhook logs

The Webhook logs screen lists every webhook event your programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production. has emitted, with delivery status, payload, and retry history. It's the first place to look when something in your app doesn't update — if the event is in the log and was delivered, the problem is in your handler; if it was sent but failed, the problem is in your endpoint or signature verification.

For configuring webhook subscriptions and verifying signatures, see Webhooks.

Viewing the log​

Open Webhook logs from the left navigation. The list shows, for each event:

  • Timestamp — when the event was emitted.
  • Event type — the webhook topic (for example, corporates.kyb.completed, iwt.completed, transfers.created).
  • Identifier — the resource the event refers to.
  • Delivery status — whether we delivered the event to your endpoint successfully.
  • Attempts — how many delivery attempts we made.

Filter by event type, delivery status, or date range to narrow the list.

Selecting an event opens a detail panel with:

  • The full request body we sent.
  • The response code your endpoint returned.
  • Per-attempt timestamps and durations.
  • The signature header we included.

Delivery status​

Each event has one of these states:

StatusMeaning
DeliveredYour endpoint returned a 2xx response within the timeout.
PendingDelivery is in progress or queued for retry.
FailedAll retries exhausted without a 2xx response.

Failed events are not retried indefinitely. If you've fixed your endpoint and need to resend, contact Weavr support — there's no self-service replay.

Sandbox and live activity​

Each environment has its own webhook log. Sandbox logs include events triggered by the Simulator and by your own API calls. Live logs reflect real customer activity.

A common testing flow:

  1. Subscribe to a topic in the Configuration > Webhooks area.
  2. Use the Simulator to trigger an event (for example, Verify Business (KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers.)).
  3. Open Webhook logs and confirm the event was emitted.
  4. Verify your endpoint received the payload and returned 2xx.

Common issues​

  • Event in log, app not updating. The webhook reached your endpoint but something downstream (queue, handler, retry logic) is failing. Check the response code in the log — if it's 2xx, the issue is on your side after acknowledgement.
  • Event in log, status Failed. Your endpoint returned a non-2xx code or timed out. Look at the response code and the attempt timestamps to debug.
  • Expected event missing. The event wasn't emitted. Confirm the underlying state change happened (use the Console to verify), and check that you're subscribed to the relevant topic.
  • Signature verification failing. See the signature verification guide in Webhooks.

Next steps​