Retrieve Webhook
Last updated
Last updated
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.
You can set your server URL on the notifications page to receive webhooks:
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
You will receive notification on each "confirmations" field update
| Key | Type | Description |
|---|---|---|
id
string*
unique identifier
toAddress
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
fromAddress
string*
sender address
valueUnits
string*
payment amount in units
value
string*
payment amount in decimal format
blockchain
string*
available values at "API value" column here
block
number*
block number in which payment was mined
txHash
string*
trasaction hash
confirmations
number*
blockchain confirmations count
assetId
string*
asset id of a payment
status
string* "pending" or "success"
pending – payment is not confirmed yet success - payment confirmed on the address
subStatus
string*
blockchain-specific status, can be used in informational purposes
statusDescription
string*
human-readable description of status field
