Endpoint
Paste your HTTPS URL, something likehttps://yourbusiness.com/webhooks/minisend, and save. Minisend starts posting signed events to it right away.
You can leave it blank if you’d rather poll the status endpoint instead. That works perfectly well; it just means your code has to keep asking rather than being told.
Secret
Your signing secret is generated the first time you open this page and shown once, in a copy-once banner like an API key. Copy it then and store it wherever your server reads its configuration from. Regenerate rotates it. The old value stops working immediately and every signature after that uses the new one, so update your server at the same time rather than later.Send a test event
The Send test button fires a signed sample payload at your endpoint on demand. It’s the quickest way to confirm your signature check works before a real payment depends on it. A test event is signed exactly like the real thing, but it isn’t recorded as a delivery and it’s never retried.Deliveries
Every delivery Minisend has attempted is listed here, newest first, with the event, the status, and the response your endpoint gave. It’s the first place to look when something didn’t reach you.
The retry schedule runs 8 attempts over roughly 33 hours, so a short outage on your side usually resolves itself with nothing for you to do.
Replay
If a delivery failed and you’ve since fixed your endpoint, Replay sends it again rather than making you wait out the schedule. It resends the exact bytes originally signed, under the sameX-Minisend-Event-Id, with a fresh timestamp and signature so your freshness check still passes.
Replay is available to owners and admins.
After five failed deliveries in a row, this page flags your endpoint as down and we get a heads-up too. Fix the endpoint, then replay what was missed rather than waiting for the remaining attempts.

