Estimate the fee required to deploy contract by template.
Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.
Developer-provided identifier for this request, used for tracing requests in Wallets API logs and the Developer Console, and when communicating with Circle Support. Must be a UUID to appear in logs. Non-UUID values are accepted by the API but are ignored by logging and tracing systems.
A unique identifier, which can be helpful for identifying a request when communicating with Circle support.
"2adba88e-9d63-44bc-b975-9b6ae3440dde"
The universally unique identifier of the resource.
"b3d9d2d5-4c12-4946-a09d-953e82fae2b0"
Request object for estimating the transaction fees for deploying a contract from a template.
The blockchain network that the resource is to be created on or is currently on.
Required along with sourceAddress if you don't provide walletId. The blockchain and walletId fields are mutually exclusive.
ETH, ETH-SEPOLIA, MATIC, MATIC-AMOY, ARB, ARB-SEPOLIA, UNI, UNI-SEPOLIA, BASE, BASE-SEPOLIA, OP, OP-SEPOLIA, AVAX, AVAX-FUJI, ARC-TESTNET, MONAD, MONAD-TESTNET "MATIC-AMOY"
Source address of the transaction. Required along with blockchain if walletId is not provided.
The sourceAddress and walletId fields are mutually exclusive.
"0x1bf9ad0cc2ad298c69a2995aa806ee832788218c"
JSON object that contains the template deployment parameters used to initialize the contract(s) on-chain.
Unique system generated identifier of the wallet. For contract deploys this wallet ID will be used as the source.
"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
Response object with estimated transaction fee values.