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.

​
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 Developer Portal 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.

​
When to Use

  • 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.

​
Capabilities

Create

Read

Sign

​
Quick Example

​
1. Create a wallet

curl -X POST https://api.beta.getpara.com/v1/wallets \
  -H "X-API-Key: sk_..." \
  -H "Content-Type: application/json" \
  -d '{"type": "EVM", "userIdentifier": "[email protected]", "userIdentifierType": "EMAIL"}'

{
  "wallet": {
    "id": "wallet_123",
    "type": "EVM",
    "status": "creating",
    "createdAt": "2025-01-01T00:00:00Z"
  },
  "scheme": "DKLS"
}

​
2. Poll until ready

curl https://api.beta.getpara.com/v1/wallets/wallet_123 \
  -H "X-API-Key: sk_..."
Once key generation completes, the wallet transitions to ready with its address and public key: 
{
  "id": "wallet_123",
  "type": "EVM",
  "status": "ready",
  "address": "0x52b54f7460187651ec28de0b9230e650ba644d1d",
  "publicKey": "0x04c3f0b85a...",
  "createdAt": "2025-01-01T00:00:00Z"
}

​
3. Sign raw bytes

curl -X POST https://api.beta.getpara.com/v1/wallets/wallet_123/sign-raw \
  -H "X-API-Key: sk_..." \
  -H "Content-Type: application/json" \
  -d '{"data": "0xdeadbeef"}'

{
  "signature": "0x..."
}

​
Next Steps

Setup

Endpoints