Sign raw bytes with a wallet’s private key share via MPC.
The input data is hex-encoded bytes. The MPC protocol signs these bytes
directly — no hashing or prefix is applied, and no chain-specific logic
is involved. This makes sign-raw suitable for any chain that uses
the same curve as the wallet’s key scheme:
To use Para wallets with an unsupported chain, create a wallet with the
matching scheme (e.g., an EVM wallet for secp256k1), pre-hash your
transaction on the client side, then call sign-raw with the hash. Derive
the chain-specific address from the wallet’s publicKey.
Use sign-transaction or sign-message instead if you want Para to
handle chain-specific serialization for EVM, Solana, or Stellar.
The response signature is a hex string (no 0x prefix). For DKLS/CGGMP
schemes this is 65 bytes: r (32) + s (32) + v (1).
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"
Hex-encoded data to sign (optional 0x prefix)
"0x48656c6c6f20576f726c64"
Encoding of data. Currently only hex is supported.
hex Expected wallet type. If provided and the wallet is a different type, the request is rejected.
EVM, SOLANA, COSMOS, STELLAR Signature
Hex-encoded signature without 0x prefix. For DKLS/CGGMP: 65 bytes (r + s + v).
"a1b2c3d4e5f6..."