Para’s REST API provides a simple HTTP surface for creating wallets and signing from your backend. UseDocumentation Index
Fetch the complete documentation index at: https://docs.getpara.com/llms.txt
Use this file to discover all available pages before exploring further.
@getpara/rest-sdk when you want typed TypeScript methods and signer adapters; use the raw HTTP API when you want
language-native fetch or cURL.
Download OpenAPI Spec
Prerequisites
To use Para, you need an API key. This key authenticates your requests to Para services and is essential for integration.Protect your API key. REST API wallets are permanently scoped to the project that created them. If you lose access
to your API key, you can rotate it safely — but deleting the project or creating a new one means losing wallet access.
See Setup → Authentication for details.
When to Use
- Programmatic (pregen) wallets — the recommended way to create wallets for users before they sign up, build agent wallets, or run server-side signing.
- Any secp256k1 or ed25519 chain — the
sign-rawendpoint is chain-agnostic. Create an EVM wallet for secp256k1 signing (works with Bitcoin, etc.) or a Solana/Stellar wallet for ed25519 signing, then hash and serialize transactions on your side. - Your backend needs wallets and you prefer REST semantics over share-backed SDK ceremonies.
- You already rely on secret-key auth + IP allowlists.
- You prefer cURL or language-native HTTP clients over SDKs.