Skip to main content
Para’s REST API provides a simple HTTP surface for creating wallets and signing raw bytes from your backend without installing a Para SDK. 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.
Don’t have an API key yet? Request access to the to create API keys, manage billing, teams, and more.
You can restrict Para REST to specific IPs by adding CIDR entries in the Developer Portal. Once you add them, requests from other IPs return 401 Unauthorized.
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-raw endpoint is chain-agnostic. Create an EVM wallet for secp256k1 signing (works with Stellar, Bitcoin, etc.) or a Solana wallet for ed25519 signing, then hash and serialize transactions on your side.
  • Your backend needs wallets but you prefer an HTTP integration instead of embedding Para SDKs.
  • You already rely on secret-key auth + IP allowlists.
  • You prefer cURL or language-native HTTP clients over SDKs.

​
Wallet Claiming

When a user signs up through your app with the same identifier used to create the wallet (e.g., the same email), the wallet is automatically claimed and transferred to their account. No server-side action is needed. For details on the client-side flow, see the Web Pregeneration guide.

​
Next Steps