Skip to main content
POST
/
api
/
v1
/
transactions
/
{winam_tx_id}
/
replay-webhook
Replay the outbound webhook for a transaction
curl --request POST \
  --url https://api.winampay.de/api/v1/transactions/{winam_tx_id}/replay-webhook \
  --header 'X-API-Key: <api-key>'
{
  "winam_tx_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "state": "<string>",
  "event": "<string>",
  "callback_url": "<string>",
  "dispatched": true,
  "message": "<string>"
}
Use replay only for recovery — when your endpoint was down and missed the original delivery. In normal operation, winam-payments fires webhooks automatically on state changes. The transaction must be in a terminal state (succeeded or failed) and have a stored callback_url.

When to use

Your callback_url returned a non-2XX response or timed out, and winam-payments exhausted its retry policy (3 attempts with exponential backoff). The transaction is already settled — you just didn’t receive the notification. Call this endpoint to re-deliver the webhook to your callback_url. Your handler must be idempotent — it may receive the same winam_tx_id more than once.

Responses

StatusMeaning
200Webhook re-dispatched to the stored callback_url
400No callback_url stored for this transaction — nothing to replay
409Transaction is not in a terminal state yet — no outcome to notify
404Transaction not found
This endpoint replays the outbound notification (winam-payments → your platform). It does not change the transaction state. Resolving a transaction that expired before a late operator confirmation is a separate, operator-only action on the internal API (POST /internal/v1/transactions/{id}/resolve).

Authorizations

X-API-Key
string
header
required

Path Parameters

winam_tx_id
string<uuid>
required

Response

Successful Response

Result of re-dispatching the OUTBOUND webhook for a transaction.

winam_tx_id
string<uuid>
required
state
string
required
event
string | null
required
callback_url
string | null
required
dispatched
boolean
required
message
string
required