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
Unique system generated JWT session token for specific user.
Developer-provided parameter used to identify this request. Useful when communicating with Circle Support.
"2adba88e-9d63-44bc-b975-9b6ae3440dde"
Body
Estimate transaction fee request
Transfer amounts in decimal number format, at least one element is required for transfer. For ERC721 token transfer, the amounts field is required to be ["1"] (array with "1" as the only element).
1["6.62607015"]Blockchain generated unique identifier, associated with wallet (account), smart contract or other blockchain objects.
"0xca9142d0b9804ef5e239d3bc1c7aa0d1c74e7350"
List of NFT token IDs corresponding with the NFTs to transfer. Batch transfers are supported only for ERC-1155 tokens. The length of NFT token IDs must match the length of amounts.
The NFT token ID.
Source address of the transaction. Required along with blockchain if walletId is not provided.
The sourceAddress and walletId fields are mutually exclusive.
"0x1bf9ad0cc2ad298c69a2995aa806ee832788218c"
System generated identifier of the token. Excluded with tokenAddress and tokenBlockchain.
Blockchain address of the transferred token. Empty for native tokens. Excluded with tokenId.
Blockchain of the transferred token. Required if tokenId is not provided.
The blockchain and tokenId fields are mutually exclusive.
ETH, ETH-SEPOLIA, AVAX, AVAX-FUJI, MATIC, MATIC-AMOY, SOL, SOL-DEVNET, ARB, ARB-SEPOLIA, UNI, UNI-SEPOLIA, BASE, BASE-SEPOLIA, OP, OP-SEPOLIA, APTOS, APTOS-TESTNET "MATIC-AMOY"
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
Transaction fee estimated