Skip to main content
Endl sends a wallet.* webhook when one of your customers’ wallets is created or deleted through the API. That covers both custodial wallets Endl creates and external wallets you register. Both events:
  • relate to one wallet, so data.id is its wlt_… id and data.customerId is the owning customer’s cus_… id
  • use the standard envelope, signature and retry rules from the Webhooks guide
Subscribing: use "eventFilter": ["wallet.*"] to receive both.

Payload fields

Standard rendering rules apply: every leaf value is a string, null fields are left out, keys are sorted, and new fields can appear without a version change. The wallet address and balance are not in the payload — read them with Get wallet.

What does not emit

  • There is no wallet.updated. Renaming a wallet sends nothing.
  • Money arriving is not a wallet event. An incoming on-chain transfer is a deposit event.
  • A failed create or delete sends nothing. Only a successful call emits.
Both events are best-effort, and both are emitted after the work has already succeeded. If the emit fails the wallet still exists, or is still deleted — the API response is the authority, not the event.

Events in detail

wallet.created

When: a custodial wallet was created, or an external wallet was registered, for a customer. What to do: store the wlt_ id against the customer. Call Get wallet if you need the address.
An external wallet looks the same with "type": "EXTERNAL":

wallet.deleted

When: a wallet was deleted. The payload describes the wallet as it was. What to do: stop offering the wallet as a source or destination.

Best practices

  • Verify the signature, then deduplicate on eventId, then act. Delivery is at least once, so the same event can arrive twice.
  • Use the API as the source of truth. If an event is missing, the Create wallet or Delete wallet response, or List wallets, tells you the real state.
  • Subscribe with wallet.* so you automatically receive new wallet events Endl adds later.