Endpoints

​

Headers

• X-API-Key (required): create in the Developer Portal and ensure it matches the environment (beta or production).
• X-Request-Id (optional): supply a UUID for tracing—Para always returns one, generating it when omitted.

​

POST /v1/wallets — Create wallet

Body:

• type: EVM | SOLANA | COSMOS
• userIdentifier: string identifier (email, phone, or partner-supplied id)
• userIdentifierType: EMAIL | PHONE | CUSTOM_ID | GUEST_ID | TELEGRAM | DISCORD | TWITTER
• scheme (optional): DKLS | CGGMP | ED25519
• cosmosPrefix (optional): string

Response:

• wallet: { id, type, status, address?, publicKey?, createdAt }
• scheme: resolved scheme

Status:

• 201 Created

​

GET /v1/wallets/:walletId — Get wallet

Response:

• { id, type, status, address?, publicKey?, createdAt }

Status:

• 200 OK

​

POST /v1/wallets/:walletId/sign-raw — Sign

Body:

• data: hex string (include the 0x prefix)

Response:

• signature: 0x-prefixed hex string

Status:

• 200 OK

​

Errors

Typical codes:

• 400 Bad Request — missing/invalid fields
• 401 Unauthorized — invalid API key or calling IP not allowlisted
• 404 Not Found — wallet not found for this partner
• 409 Conflict — duplicate type + scheme + userIdentifier combination
• 500 Internal Error