Overview
Coinut sends webhook events to your registered callback URL when important events occur. All webhooks:- Use the
POSTmethod - Send a JSON body
- Expect an HTTP
200response within 30 seconds - Use the
WebhookEventenvelope documented inrampdocs.json
Setting Up Webhooks
1
Register callback URL
Send
POST /callback-url with your HTTPS endpoint.2
Subscribe to events
Send
POST /subscribed-events with the event types you want to receive.3
Verify signature
rampdocs.json does not define a webhook signature header or verification algorithm. If Coinut enables signed webhooks for your environment, follow the latest operational guidance provided with your partner account.4
Acknowledge receipt
Return HTTP
200 within 30 seconds. The exact retry policy is not defined in rampdocs.json, so your handler should be idempotent and safe to receive duplicate deliveries.Webhook Delivery
Event Types
Webhook Payload Examples
Signature Verification
rampdocs.json does not define a webhook signature header or signature-construction method. If your partner setup includes signed webhook delivery, use Coinut’s current operational guidance for header names, canonicalization rules, and retry handling.
Best Practices
- Verify signatures when enabled. If Coinut provides a webhook signature mechanism for your environment, validate it before processing the payload.
- Handle idempotently. Use the
event+payload.idcombination to prevent duplicate processing. - Return 200 quickly. Respond immediately, then process the event asynchronously.
- Log everything. Store raw payloads and headers for debugging.
- Expect retries. The same event may arrive multiple times if your handler is slow.

