Authorizations
Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are requred to make a successful request.
Headers
Developer-provided parameter used to identify this request. Useful when communicating with Circle Support.
"2adba88e-9d63-44bc-b975-9b6ae3440dde"
Path Parameters
The universally unique identifier of the resource.
"b3d9d2d5-4c12-4946-a09d-953e82fae2b0"
Body
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 "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. Required when sourceAddress and blockchain are not provided.
Mutually exclusive with sourceAddress and blockchain.
For contract deploys this wallet ID will be used as the source.
"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
Response
Response object with estimated transaction fee values.