Skip to main content
POST
/
v1
/
signature
/
sign
Sign Transaction
curl --request POST \
  --url https://api.example.com/v1/signature/sign \
  --header 'Content-Type: application/json' \
  --data '
{
  "chainReference": "<string>",
  "unsignedTxHex": "<string>",
  "keyId": "<string>",
  "coinType": 123,
  "accountIndex": 123,
  "metadata": {}
}
'
{
  "signature": "<string>",
  "digest": "<string>",
  "algorithm": "<string>"
}

​
Sign Transaction

Sign an unsigned transaction using the appropriate protocol adapter (EVM, Solana, etc.). The signing is performed securely within the TEE.

​
Request

​
chainReference
string
required
Chain identifier (e.g., eip155:1)
​
unsignedTxHex
string
required
Unsigned transaction in hex format
​
keyId
string
required
KMS key identifier
​
coinType
integer
required
BIP-44 coin type (60 for ETH, 501 for SOL)
​
accountIndex
integer
required
Account index for key derivation
​
metadata
object
Additional signing metadata

​
Response

​
signature
string
Transaction signature in hex format
​
digest
string
Message digest that was signed
​
algorithm
string
Signing algorithm used (e.g., secp256k1)

​
Example

curl -X POST https://api.axonvault.io/v1/signature/sign \
  -H "X-Access-Key: ak_live_abc123" \
  -H "X-Signature: 5d41402abc4b2a76b9719d911017c592" \
  -H "X-Timestamp: 2024-01-15T10:30:00Z" \
  -H "Content-Type: application/json" \
  -d '{
    "chainReference": "eip155:1",
    "unsignedTxHex": "0xf86c0a8502540be400825208...",
    "keyId": "key_xyz789",
    "coinType": 60,
    "accountIndex": 0
  }'

​
Response Example

{
  "signature": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef1c",
  "digest": "0xabc123def456789...",
  "algorithm": "secp256k1"
}

​
Supported Chains

Chain TypeCoin TypeAlgorithm
EVM (Ethereum, Base, etc.)60secp256k1
Solana501ed25519
Bitcoin0secp256k1

​
Errors

Error TypeStatusDescription
invalid_request400Missing required fields
key_not_found404Key ID not found
signing_failed500Signing operation failed
policy_denied403Signing blocked by policy

​
Security

All signing operations are performed within the Trusted Execution Environment (TEE). Private keys never leave the secure enclave.