Binance Web3 Connector JS
    Preparing search index...

    Request parameters for submitRfqOrder operation in TradingApi. SubmitRfqOrderRequest

    interface SubmitRfqOrderRequest {
        nonce?: string;
        quoteId: string;
        recvWindow?: number | bigint;
        requestId: string;
        signingScheme?: string;
        userSignature: string;
        vendor: SubmitRfqOrderVendorEnum;
    }
    Index

    Properties

    nonce?: string

    Unique request identifier for anti-replay; falls back to X-OC-SIGN if omitted.

    TradingApiSubmitRfqOrder

    quoteId: string

    rfq.orderId from the /swap response. The backend uses this to look up the vendor and chain context required to forward the signed order.

    TradingApiSubmitRfqOrder

    recvWindow?: number | bigint

    Allowed time deviation in milliseconds (default: 5000, max: 60000).

    TradingApiSubmitRfqOrder

    requestId: string

    Idempotency key (UUID v4). Within 30 minutes, re-submitting with the same requestId returns the original result without re-calling the vendor. Generate a new UUID for each new order; reuse the same UUID when retrying the same attempt.

    TradingApiSubmitRfqOrder

    signingScheme?: string

    Signing scheme from rfq.signingScheme in the /swap response. Optional — when omitted the backend infers the default per vendor.

    TradingApiSubmitRfqOrder

    userSignature: string

    EIP-712 signature of rfq.typedDataToSign from the /swap response. Must be a hex string with 0x prefix (132 chars = 0x + 65 bytes). The signing wallet must match userWalletAddress used in /quote. The backend automatically corrects Ethereum v values 00/01 to 1b/1c.

    TradingApiSubmitRfqOrder

    RFQ vendor name — must match rfq.vendor from the /swap response. The backend validates this against quoteId to prevent misrouted submissions.

    TradingApiSubmitRfqOrder