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"
Body
Creates a transaction for a developer request.
Universally unique identifier (UUID v4) idempotency key. This key is utilized to ensure exactly-once execution of mutating requests. To create a UUIDv4 go to uuidgenerator.net. If the same key is reused, it will be treated as the same request and the original response will be returned.
"a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
newScaCore displays the version of the SCA available for upgrade. For a list of supported versions, refer to the developer documentation.
circle_6900_singleowner_v2 "circle_6900_singleowner_v2"
A base64 string expression of the entity secret ciphertext. The entity secret should be encrypted by the entity public key. Circle mandates that the entity secret ciphertext is unique for each API request.
"M8OAwbJ8rMsPd8+NT4xRDBDJSNqUKAvJeWPyuwZSlVXgRucogAlBxjvjIw4nsKeJ4hejjlpmyaaJrusHm6zsvy4BLuL1an3dYn3wORjYf3sU4QN9Rdk9OJxZvE5hDNPq7okucvb1eElxPVREZvr4ew7sh4ktmwDrwWFUYwKoly4fEzxYI9zvVpCY9xPSgkA5m3u1/P2vMYZ0QFtn8lRZxCuTyc4wRLpT9TOaK46CEXCakmAYaYWnLkl18QXOSY6FhCbGm+zQ2Uu4cUPU/bqjIyQIB80ut3drInDzysQLE/FJjcJW9+q+E75LKGKnrp2zCg/Xv3TEvru9a2A0vd7InZ9kNuxnPPFc1JSO7BT2TPP89YcLO0OmtRiGoXPlYzXuNIfUsVQ5/FW9FPp4qp+iMPrAidsjQrskHPxhW92GeezLpOSkUl7lAWQoioYED979mqGfzNIZTF5Ob6fJifboiwhOab6sAKnxmvWjgFnW/bZ5a8xkzgPc4RHpIejot1Q7fpT+67eA+DVxvUqakJI6t3iEaZTNITCSU2Cfj1oyCQfrZGf9tauW49rO1zYHKoV4z9ylymOWtCUk641iyxwFCNSW47CDsc0M8iI4J6JqsNMpQuR9sdWVhROi5yn9UR7ac7pizB3dFmc0/qjtTRoYStaaSEYg3L5woALv5kAA2j4="
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"
A dynamic blockchain fee level setting (LOW, MEDIUM, or HIGH) that will be used to pay gas for the transaction. Calculated based on network traffic, supply of validators, and demand for transaction verification. Cannot be used with gasPrice, priorityFee, or maxFee.
Estimates for each fee level can be obtained through the POST /transactions/transfer/estimateFee API.
LOW, MEDIUM, HIGH "MEDIUM"
The maximum units of gas to use for the transaction. Required if feeLevel is not provided.
Estimates for this limit can be obtained through the POST /transactions/transfer/estimateFee API.
GasLimit override (only supported for EOA wallets): Using gasLimit together with feeLevel, the provided gasLimit is required to be greater or equal to feeLevel estimation and will override the estimation's gasLimit.
"21000"
For blockchains without EIP-1559 support, the maximum price of gas, in gwei, to use per each unit of gas (see gasLimit). Requires gasLimit. Cannot be used with feeLevel, priorityFee, or maxFee.
Estimates for this fee can be obtained through the POST /transactions/transfer/estimateFee API.
For blockchains with EIP-1559 support, the maximum price per unit of gas (see gasLimit), in gwei. Requires priorityFee, and gasLimit to be present. Cannot be used with feeLevel or gasPrice.
Estimates for this fee can be obtained through the POST /transactions/transfer/estimateFee API.
"5.935224468"
For blockchains with EIP-1559 support, the “tip”, in gwei, to add to the base fee as an incentive for validators.
Please note that the maxFee and gasLimit parameters are required alongside the priorityFee. The feeLevel and gasPrice parameters cannot be used with the priorityFee.
Estimations for this fee can be obtained through the POST /transactions/transfer/estimateFee API.
"1.022783914"
Optional reference or description used to identify the transaction.
"grouptransaction123"
Response
Returns the existing transaction if the idempotency key matches a previous successful request.