Delivery to your registered HTTPS receiver
Verify raw bytes with the endpoint secret: HMAC-SHA256(timestamp + '.' + raw body), ±5 minutes. Durably deduplicate event.id. Deliveries may be delayed, duplicated and out of order; up to eight attempts. Respond within 10 seconds after durably accepting the event.
Verify raw bytes with the endpoint secret: HMAC-SHA256(timestamp + '.' + raw body), ±5 minutes. Durably deduplicate event.id. Deliveries may be delayed, duplicated and out of order; up to eight attempts. Respond within 10 seconds after durably accepting the event.
Header Parameters
^\d+$^[a-f0-9]{64}$Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
Example Requests
/clientEventNetwork fee estimates GET
Current low, medium and high fee estimates for one network, in the network coin and USD, for a transfer, a token transfer and a swap. Estimates for previews and for choosing a fee cap: the network sets the final fee when a transaction is broadcast. Amounts are the tier rate multiplied by the standard job sizes in data.units. Read-only; the same for every workspace.
Create a wallet for one of your customers POST
Proposes one wallet under organisation policy; never approves it. Opt-in per organisation: until MegTrust enables wallet creation for yours, every call returns 403 wallet_create_not_enabled and nothing is created. Safe to retry: one Idempotency-Key and one external_ref per wallet, each unique within the organisation. Same key and body return the current state — 202 while pending (no wallet yet), 201 or 200 with the wallet once active, 422 wallet_create_failed if the create did not go through. Retrying a 422 with the same key is always safe: a failed or expired create is tried again for the same wallet, up to three proposals; a decline under policy, or a create that failed three times, is final and keeps answering 422 from the stored request with no new attempt. A different body under the key, or the external_ref under another key, returns 409. Every request carries `customer`; MegTrust screens that customer first, so a new request answers 202 while screening runs. A customer who does not pass is refused for good: 422 wallet_create_refused, and no wallet is proposed.