Sign a transaction with a wallet’s private key share via MPC.
EVM: Provide unsigned transaction fields as a JSON object and the endpoint
will RLP-encode them, sign via MPC, and return a fully serialized signed
transaction (hex-encoded with 0x prefix) ready for broadcast.
Solana: Provide a base64-encoded serialized Solana transaction (as built
by @solana/web3.js). Both legacy Transaction and versioned
VersionedTransaction (v0, with Address Lookup Tables) are accepted; the
endpoint auto-detects the format, signs via MPC, and returns the signed
transaction as a base64 string ready for broadcast.
Set top-level broadcast: true to broadcast the signed transaction for EVM
or Solana wallets. Broadcasted calls create a persisted transaction record,
return txHash and transactionId, and set x-transaction-id. Omitted
broadcast remains sign-only and writes no transaction-history row. Stellar
wallets do not support broadcast: true.
Stellar: Provide a base64-encoded Stellar transaction envelope (XDR) in
the transaction field and the network passphrase in networkPassphrase.
The endpoint computes the transaction hash, signs it via MPC, and returns
the signed transaction as a base64-encoded XDR string.
Documentation Index
Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
Use this file to discover all available pages before exploring further.
Your partner secret key (server-side only)
UUID for request tracing. Para returns one if omitted.
Unique key for safe retries on POST endpoints. If a request with the same key is received within 24 hours, the original response is returned without re-executing. Recommended format: UUID v4. Max length 256 characters. Returns 422 if the same key is reused with a different request body. Returns 409 if a request with the same key is still being processed.
256Wallet ID
"0a1b2c3d-4e5f-6789-abcd-ef0123456789"
EVM: JSON object with unsigned transaction fields.
Solana: base64-encoded serialized transaction string.
Stellar: base64-encoded XDR transaction envelope string.
The API differentiates by the wallet's type (determined by walletId).
Objects are treated as EVM transactions; strings are treated as Solana
or Stellar transactions depending on the wallet type. For Stellar
wallets, networkPassphrase is required.
Stellar network passphrase. Required when the wallet referenced by walletId is a STELLAR wallet. Ignored for other wallet types.
"Public Global Stellar Network ; September 2015"
Solana network to broadcast to when broadcast: true. Uses the same environment rules as POST /transfer.
SOLANA, SOLANA_DEVNET When true, broadcast the signed EVM or Solana transaction, create a persisted transaction record, and return txHash plus transactionId. Omitted or false remains sign-only. Stellar wallets reject broadcast: true.
Signed transaction
Signed transaction ready for broadcast. EVM: RLP-encoded hex string with 0x prefix. Solana: base64-encoded string. Stellar: base64-encoded XDR string.
"0x02f8..."
Transaction hash. Present only when broadcast: true succeeds.
"0x1234abcd..."
Persisted transaction record id. Present only when broadcast: true creates a transaction-history row.
"550e8400-e29b-41d4-a716-446655440000"