Retrieve Webhook
Introduction
We will notify you on each incoming payment to a Proxy Wallet and when of assets transferred to your Omnibus accounts (Forwarding webhooks).
We will notify you up to 10 times until your server respond http success status (200-299)
We use exponential backoff with a 1-minute delay as a seed value, so it will retry at most 10 times spaced after 1 minute, 2 minutes, 4 minutes, 8 minutes, etc.
In order to maintain non-custodial nature of Curra - we strongly recommend to double-check incoming webhooks via your own RPC.
Setup
You can set your server URL on the notifications page to receive webhooks:
Webhook payload
In order to authorize Curra notifications, like incoming payments notifications, you should compare webhook request's X-API-KEY
header with your API key.
Method: POST
Headers:
content-type:
application/json
x-api-key:
your_api_key
GET
https://yourwebsite.com/curra/incoming-payment-hook
Body:
Key | Type | Description |
---|---|---|
| string* | unique identifier |
| value: string* uniqueId: string* meta: string | value – receive address uniqueId - uniqueId provided on address creation, generated if not provided meta – meta provided on address creation |
| string* | sender address |
| string* | payment amount in units |
| string* | payment amount in decimal format |
| string* | available values at "API value" column here |
| number* | block number in which payment was mined |
| string* | trasaction hash |
| number* | blockchain confirmations count |
| string* | asset id of a payment |
| string* "pending" or "success" | pending – payment is not confirmed yet success - payment confirmed on the address |
| string* | blockchain-specific status, can be used in informational purposes |
| string* | human-readable description of status field |
Examples:
You will receive notification on each "confirmations"
field update
Last updated