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
Schema for the request payload to sign a transaction.
System-generated unique identifier of the resource.
"c4d1da72-111e-4d52-bdbf-2e74a2d803d5"
Raw transaction string that needs to be signed. Excluded with transaction. Required without transaction.
Required to be base64 encoded for NEAR, Solana chains. Required to be hex encoded for EVM chains.
"AgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAIAAQROrEbiYfF3zCII9..."
Transaction object in JSON that needs to be signed. Excluded with rawTransaction. Required without rawTransaction.
NOTE: This field is only supported by EVM chains.
"{\"nonce\":1,\"to\":\"0x9e4ebf23f713268b8e72cd162337f20c536357c9\",\"value\":\"10000000000000000\",\"gas\":\"21000\",\"maxFeePerGas\":\"42000000000\",\"maxPriorityFeePerGas\":\"25000000000\",\"chainId\":80002}"
The human readable explanation for this sign action. Useful for presenting with extra information.
"Transfer USDC to Sam"
Response
Signature already exists