/rfq/:id/confirm
authwriteexample onlyThe response below is an example, not a live call. Confirming needs the priced RFQ and your EIP-712 signature over Terms. Run it from your authenticated desk. The request on the left is exact — run it from your authenticated client.
Path params
Body
Identity
The relayer identifies the caller from this address — no signature. A trade still binds only with the two EIP-712 Terms signatures.
Bearer token · optional
curl -X POST "https://app.crxfx.com/svc/relayer/rfq/0x9f2c4a1b7e3d8c6f05a9b2d4e1f6c3a8b7d5e2f1c0a9b8d7e6f5c4b3a2918070/confirm" \
-H "X-CRX-Address: 0xd403e4e3239943fae744f44776476e60f54ed167" \
-H "Content-Type: application/json" \
-d '{
"signature": "0x"
}'Response
Press Example to see a sample response — this call opens a live trade and runs from your authenticated desk.
Confirm a priced RFQ by submitting an EIP-712 signature over the returned Terms. Authentication is required.
- Path:
id: the priced RFQ id. - Body:
{ "signature": "0x…" }. - Returns:
{ "quote_ref": "0x…", "valid_until": 1780313385 }. The match is now firm and is anchoring on-chain in the background.