Send a test event
In the dashboard, open Developers, then Events, and choose Send test event. Pick an event from the Event catalog and send it. It is a real delivery. The event goes to the URL subscribed to it, signed with that URL’s secret, on the same retry schedule as any other event. The attempt appears in the Events list with its response code, and you can replay it. It is marked.data.test is true on every test event. Check it before your handler acts on anything.
Nothing behind it exists. The payload has the shape of the real event. No record is created and no money moves, so its ids return nothing when you read them. For an rfi.* event you can pick one of your own requests for information, and the payload is built from it.
It needs a subscribed URL. A test event goes only where a real one would. If no active URL subscribes to the event, it goes nowhere. The dialog tells you before you send.
The button also works in production, where it reaches your production URL. It needs a role that manages webhooks. See Roles and permissions.
Make an event happen
The sandbox produces real events from real actions, so the way to test a handler is to drive the lifecycle that emits what you want to receive.
Your first complete payment in sandbox walks the whole sequence, and every step of it emits.