Introduction

Sovera Crypto as a Service lets you onboard users, hold and move crypto, trade, and pay out—all over one REST API. You send JSON, you get JSON back, and every response uses standard HTTP status codes.

Three API groups

The API splits into three groups. Pick the one that matches what you're doing:

• SX Connect—onboard and configure with your Owner API Key. Manage the user lifecycle, issue user tokens, and set fees, currencies, and account data.
• SX Users—act for each end user with their token. Create wallets and addresses, request quotes, trade, transfer, and withdraw.
• SX Customers—manage your customers (tenants) with your Bearer session. Configure customer accounts, deposit email pollers, and webhooks.

What you'll build

• Onboard and manage users—see Users.
• Create wallets and deposit addresses—see Wallets.
• Quote and place trades—see Trading.
• Move funds between wallets—see Transfers.
• Pay out with OTP confirmation—see Withdrawals.
• Read balances and history—see Account data.

Authentication and base URL

Send every request over HTTPS to:

https://api.sandbox.sovera.io/sovx/v1

Authenticate by audience: x-api-key (owner) for SX Connect, Authorization: Bearer (user token) for SX Users, and Authorization: Bearer (account session) for SX Customers. See Authentication for keys, tokens, and scopes. Keep your keys secret—never commit them to source control or ship them in client-side code. Calls over HTTP or without a key fail.

Core entities

Four entities anchor every flow:

• Customer—your platform account. Holds credentials, webhooks, and monetization settings.
• User—an end user under your customer. Onboarding creates the user and unlocks wallets.
• Wallet—a per-user container that holds balances across currencies.
• Address—a deposit address on a wallet, issued per currency and network.

Start here

New to the API? Follow Getting started, then walk the user onboarding flow end to end.