Skip to main content

Webhook tester

Build the request the OMS sends for any event and fire it at your own endpoint, before a single real delivery exists. Pick the event, describe your endpoint, then run the generated command from your shell: your receiver gets the same envelope, the same headers and the same minified body a real delivery carries, so you can write and debug it while Calicantus is still configuring your webhook.

note

The page assembles a command — it never sends anything itself, and the credentials you type stay in your browser.

Identical to a real delivery: the method, the envelope, the payload of the event, the compact JSON body and the headers the OMS sets.

Different, because the call leaves your machine and not the OMS: the source IP, the order and the casing of the headers, and the TLS handshake. The User-Agent is the HTTP client the OMS uses today and changes when that client is upgraded, so treat it as an example rather than a value to match on. The retries with exponential backoff are not reproduced either: the command sends the event once.

1 · Pick the event

PaymentExternalTransaction · refund_requested — documented in Payment transaction — refund requested

2 · Describe your endpoint

Credentials and headers typed here are only interpolated into the command below: this page stores nothing and sends nothing.

3 · Send it

Request body

Replace data.id and the payload ids with records of your own; the command follows along.

Command
curl -sS -X POST 'https://your-endpoint.example.com/oms/webhooks' \
-H 'Content-Type: application/json' \
-H 'OMS-Webhooks-Version: v1' \
-H 'User-Agent: rest-client/2.1.0 (linux x86_64) ruby/3.2.2p53' \
-H 'Accept: */*' \
-H 'Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3' \
--http1.1 \
--max-time 10 \
-w '\n→ HTTP %{http_code} in %{time_total}s\n' \
-d '{"id":"019f935c-395e-723d-a53b-08adff459954","data":{"id":1234,"resource":"PaymentExternalTransaction","event":"refund_requested","timestamp":"2026-07-24T09:02:02+00:00","payload":{"id":1234,"number":"refund-1234","amount":"-10.00","currency":"EUR","reference_code":"refund-reference-1234","merchant":{"code":"merchant-code"},"sale_transaction":{"id":5678,"number":"sale-5678","amount":"10.00","currency":"EUR","reference_code":"sale-reference-5678"}}}}'

The body travels minified over HTTP/1.1, as the OMS sends it. --max-time 10 applies the same budget a real delivery gives you, and the last line prints the status code and how long your endpoint took.

What your endpoint must do with it​

The generated command prints the status code and the elapsed time on its last line, which is exactly what the OMS judges a delivery by:

  • answer 200 — any other status counts as failed and starts the retry sequence;
  • answer within 10 seconds — the command stops there too, so a curl: (28) is a delivery the OMS would have given up on;
  • process each event id once — retries repeat the same id, and your endpoint may well receive an event it has already handled (typically when it answered after the timeout). Send the command twice with the same id and make sure the second one changes nothing on your side.

The payload values are placeholders — replace data.id and the ids inside payload with records of your own, and check that your receiver reads them where it expects to. What every event carries is documented in Events; the envelope and the delivery rules in Introduction to Webhooks.