Skip to main content

Base URL

All requests go to:
Staging environment:

Authentication

There are two authentication methods depending on the endpoint:

API Key (Merchant endpoints)

Used for /auth/authenticate-client and /secure/* endpoints. Pass your key in the api-key header:

Client Token (Client endpoints)

Used for /client/* endpoints. Pass the JWT in the Authorization header:
See the Authentication guide for how to generate client tokens.

Response Format

All responses follow the same envelope:

Success

Error

The requestId is a UUID generated for each request. Include it when contacting support about specific errors.

Rate Limits

Rate limits vary by endpoint and merchant verification status. Numbers below are per-merchant — limits are shared across all clients of the same merchant for /client/* routes.

Client endpoints

Deposits additionally enforce a per-client guard: max 5 concurrent active deposits + max 10 deposits per rolling 5-minute window per (merchant, clientSteamId).

Secure (merchant) endpoints

When you hit a rate limit, you’ll receive a 429 response with error code 1005 (RATE_LIMITED).

Versioning

The API uses URI-based versioning. Client and secure endpoints are version-neutral (no version prefix needed). Call them directly:

Prices

All prices in the API are in USD (dollars), not cents. For example, 10.75 means $10.75.

Game Parameter

Most endpoints accept a game parameter: If omitted, defaults to 730 (CS2).