Binance Web3 Connector JS
    Preparing search index...

    Interface BuildSwapTransactionResponseDataRfq

    RFQ order payload. Present only when executionMode=RFQ. Contains the EIP-712 typed data to sign, the target vendor, the signing scheme, and (when requested) the approve transaction data.

    BuildSwapTransactionResponseDataRfq

    interface BuildSwapTransactionResponseDataRfq {
        signatureData?: string[];
        signingScheme?: string;
        txType?: string;
        typedDataToSign?: string;
        vendor?: string;
    }
    Index
    signatureData? signingScheme? txType? typedDataToSign? vendor?
    signatureData?: string[]

    Approve transaction data, present only when approveTransaction=true was passed and the from-token is an EVM ERC-20. Each element is a JSON string containing approveContract (the spender address, resolved per vendor: InchFusion→router, PcsXRfq→Permit2, CowSwap→VaultRelayer) and approveTxCalldata (the ERC-20 approve() calldata). Empty list otherwise.

    BuildSwapTransactionResponseDataRfq

    signingScheme?: string

    Signing scheme required by this vendor. Pass this as signingScheme in POST /order/submit.

    BuildSwapTransactionResponseDataRfq

    txType?: string

    Transaction type for this RFQ order. Currently always EIP712 (all three RFQ vendors use EIP-712 typed-data signing); reserved for future signing schemes.

    BuildSwapTransactionResponseDataRfq

    typedDataToSign?: string

    EIP-712 typed data payload for eth_signTypedData_v4, serialized as a hex string (or JSON-encoded string). Sign with the wallet that matches userWalletAddress from /quote. Pass the resulting signature as userSignature in POST /order/submit.

    BuildSwapTransactionResponseDataRfq

    vendor?: string

    RFQ vendor that will settle this order on-chain. Pass this as the vendor field in POST /order/submit.

    BuildSwapTransactionResponseDataRfq

    Settings
    Member Visibility

    On This Page
    Properties