Generate funding presign data
Returns the Permit2 EIP-712 payload that the trader must sign for funding operations. fundingMode net option is supported for maker funding requests.
When fundingMode is delegate, the response instead contains two typed-data payloads: one for the trader to sign (a zero-amount authorization) and one for the funder to sign (carrying the actual delivery amount). Delegate mode supports both maker and taker, requires funderAddress and recipientAddress, and accepts exactly one contract trade ID per request.
Authorizations
Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.
Body
Request body for generating funding presign data
List of contract trade IDs. Exactly one contract trade ID is supported when fundingMode is delegate.
1["10", "11", "12"]The type of trader.
maker, taker Funding mode for the presign request. net is supported for maker funding requests only; delegate is supported for both maker and taker.
gross, net, delegate Address of the funder wallet that will deliver tokens on the trader's behalf. Required when fundingMode is delegate.
"0x1234567890abcdef1234567890abcdef12345678"
Address that receives the delivered tokens. Required when fundingMode is delegate.
"0xabcdef1234567890abcdef1234567890abcdef12"
Response
Funding presign data generated successfully
- TraderFundingPresign
- DelegateFundingPresign
Response containing Permit2 EIP-712 typed data for funding operations. For gross and net funding modes, contains the trader's Permit2 typed data along with deliverables and receivables. For delegate funding mode, contains separate typed-data payloads for the trader and the funder. No discriminator is defined because the response body carries no fundingMode field; the variant is determined by the fundingMode sent in the request, and the two variants have mutually exclusive required properties.