Choose This Path If
- Your backend owns user authentication or maps existing users to Para wallets.
- You want to create or pregenerate wallets before users visit your app.
- You want HTTP endpoints, cURL, or language-native clients instead of a client SDK.
- You want server-side helpers for sessions, pregeneration, automation, or chain operations.
REST API and Node & Server are related but not identical. REST API is the direct HTTP surface. Node & Server is the SDK path for backend JavaScript integrations.
Integration Lifecycle
1
Create a Para project
Create a project and API key in the Developer Portal, then review Developer Portal setup. Protect backend API keys before making requests.
2
Pick REST API or server SDK
Use the REST API for direct HTTP wallet operations. Use Node & Server when you want server-side SDK helpers in a JavaScript backend.
3
Connect users and wallets
For REST, start with REST setup, REST SDK, multi-wallet setup, or permissions. For server SDK, start with sessions or pregen.
4
Sign from the backend
Use the REST endpoints or server SDK chain guides for EVM, Solana, Cosmos, or Stellar signing.
5
Prepare for launch
Review IP restrictions, API key handling, webhooks, the Go Live Checklist, and Production Deployment.