Hyperscaled API

Build a prop-trading business on our infrastructure

The Hyperscaled API gives you everything behind a modern prop firm — identity verification, payments, funded accounts, live trading, and payouts — behind one multi-tenant REST API. This is the documentation for the same endpoints that power the Vanta reference app you're looking at.

Every call is authenticated, multi-tenant, and isolated to your app. You bring the UI; we run the regulated, capital, and market plumbing.

1

Get your credentials

Each integrating app is a tenant with its own OAuth client_id and client_secret. Request access and, once approved, you'll get a one-time link to retrieve them:

  1. Submit the Request access form (company, contact, use case).
  2. We provision your network identity and approve the request — approval is manual.
  3. You receive an email with a one-time link to reveal your client_id and client_secret (the secret is shown once).

Running locally? You can self-approve from the admin console — see the Quickstart. Confirm an app's scopes and tenant identity anytime via GET /v2/apps/me. It does not return the client_id or the secret — both are shown only once, at the one-time reveal link, and app_id is a bare UUID, not the hsc_-prefixed client_id. The secret is rotate-only and never readable again.

2

Make your first request

Your first request
# 1. Exchange your app credentials for an access token (form-encoded, not JSON)
curl -X POST http://localhost:8000/v2/oauth/token \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d grant_type=client_credentials \
  -d client_id=hsc_... \
  -d client_secret=hsk_... \
  -d scope=api

# 2. Use the token to call the API
curl http://localhost:8000/v2/auth/me \
  -H "Authorization: Bearer <access_token>" \
  -H "X-Session-Token: <end_user_session>"

Two layers of auth

Your app authenticates with OAuth client credentials. Your end users get a session token after signing up / logging in, passed as X-Session-Token. See Authentication.

Explore the flows