Skip to main content
Para’s REST API provides a simple HTTP surface for creating wallets and signing from your backend. Use @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. One lifecycle route set supports EVM, COSMOS, SOLANA, STELLAR, and SUI. The wallet’s type determines its address and chain-specific signing behavior; you do not switch to a different API namespace for each wallet type. 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. Deleting the project or creating a new one means losing wallet access. See Setup → Authentication for details.

​
When to Use

  • Programmatic (pregen) wallets: Create wallets for users before they sign up, build agent wallets, or run server-side signing.
  • All five supported wallet types: Create and manage EVM, Cosmos, Solana, Stellar, and Sui wallets through the same routes.
  • Other secp256k1 or Ed25519 chains: The sign-raw endpoint is chain-agnostic. Use an EVM or Cosmos wallet for secp256k1 signing, or a Solana, Stellar, or Sui wallet for Ed25519 signing, then handle the chain-specific serialization and hashing 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.

​
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. See Wallet lifecycle by wallet type for the REST signing boundary after a claim.

​
Next Steps