Skip to main content
Dashboard → Webhooks is where you tell us where your server is, and see every message we’ve sent it. If you’d rather your code was told about payments than have to keep checking, set this up first. For what the events contain and how to check a signature, see Webhooks.

Endpoints

Paste your HTTPS URL, something like https://yourbusiness.com/webhooks/minisend, and save. We start sending signed messages to it straight away. You can leave it blank if you’d rather check the status endpoint yourself. That works fine. It just means your code has to keep asking instead of being told.

More than one product

Running more than one product on this account? Click Add endpoint to add up to two more, three in total. Under each URL, pick the products it receives: Checkout, Off-ramp, Onramp, and Wallet API. Then save.
  • Anything no endpoint picks goes to endpoint 1, so you never lose events by narrowing one.
  • Endpoint 1 needs a URL while you have other endpoints, since it’s where those leftover events go.
  • Two endpoints can’t share a URL.
  • All of them use the one secret below.
See More than one endpoint for how events are split.

Secret

We create your secret the first time you open this page and show it once, like an API key. Copy it then, and store it wherever your server keeps its settings. Regenerate replaces it. The old secret stops working straight away and every message after that uses the new one, so update your server at the same time.
Lost it? Regenerate a new one. Nobody can read an existing secret, not even you, which is also what keeps it safe.

Send a test event

Each endpoint has a Send test event button that sends a signed sample message to that URL whenever you like. Save your changes first. It’s the quickest way to check your signature check works before a real payment depends on it. A test message is signed exactly like a real one, but it isn’t added to the list below and we never retry it.

Deliveries

Every message we’ve tried to send you, to any of your endpoints, is listed here, newest first, with the event, how it went, and what your server replied. Open one to see the URL it went to. It’s the first place to look when something didn’t reach you. We try up to 8 times over about 33 hours, so if your server is down briefly, it usually sorts itself out with nothing for you to do.

Replay

If a message failed and you’ve since fixed your server, Replay sends it again straight away, to the endpoint it was first sent to, instead of waiting for the next retry. It’s exactly the same message, with the same X-Minisend-Event-Id, plus a fresh timestamp and signature so your time check still passes. Owners and admins can replay messages.
After five consecutive failed messages to one endpoint, this page marks that endpoint as down. Each endpoint is checked separately. Fix your server, then replay what you missed instead of waiting for the remaining tries.