0xDocs 0x.limo

Docs / REST API

Payments and top-ups

Partly live

The player's 0x balance and card top-ups (USDT networks and Bitcoin), paid games and store orders, play tickets, developer revenue and USDT payouts, plus in-game purchases and subscriptions (switched off).

Money on 0x runs through one place: the player's 0x balance, in US cents. Players top it up with a card through the USDT checkout. Paid games, inventory purchases and, once they are switched on, in-game purchases and subscriptions are paid from it. Developers earn the sale price minus the platform fee and are paid out in USDT.

FeatureOn 0x.limo
Balance and top-ups (Ethereum, Tron, Arbitrum, BSC, Polygon USDT, and Bitcoin)live
Paid games (store orders paid from the balance)live
Developer revenue and USDT payoutslive
Play tickets (POST /v1/apps/{appid}/play-ticket)not enabled yet: answers 503 play_tickets_closed
In-game purchases (/v1/.../iap/...)off: answers 404 in-game purchases are off
Subscriptions (/v1/me/subscriptions, plans)off: answers 404 subscriptions are off

#The balance

bashtested
curl -s https://api.0x.limo/v1/me/wallet -H "Authorization: Bearer $ZEROX_TOKEN"
json
{"currency": "USD", "balance": 2500, "balanceUsd": "25.00", "topups_enabled": true,
 "topup_min": 2000, "topup_max": 50000,
 "networks": [{"id": "tron", "name": "Tron", "token": "USDT", "standard": "TRC-20", "...": "..."}],
 "last_network": "tron", "history": [], "topups": []}

balance is in cents. Top-ups are whole dollars from $20 to $500.

#Top-ups

RouteDoes
POST /v1/me/wallet/estimate {amountUsd}what the card would be charged on each network (cached a minute)
POST /v1/me/wallet/topups {amountUsd, network?}start a top-up → 201 with the checkout URL to send the player to
GET /v1/me/wallet/topupsthe player's top-ups, newest first
GET /v1/me/wallet/topups/{id}one top-up (the return page polls it) and the new balance
POST /v1/me/wallet/topups/{id}/cancelcancel an open top-up (409 once a payment has arrived)

A top-up moves through pending → confirming → paid. The other end states are paid_short, expired, failed, mismatch and resolved. The balance is credited when the payment confirms. Starting a top-up is limited to one every 20 s per account (burst 10).

Top-ups are a player feature: the launcher and https://0x.limo show them. Your game only needs the balance when it sells something.

A listing's price is "free" or {amount, currency} in minor units (USD; $0.99 to $1000). It is set when you submit the listing. Once approved, the catalog shows store.price with store.free: false, and only buyers own the game.

RouteDoes
POST /v1/store/orders {appid, idempotency_key?}buy a game, paid at once from the balance → 201 {order: {status: "paid"}, paid_from: "wallet", wallet}
GET /v1/me/orders / GET /v1/me/orders/{id}the player's orders
POST /v1/me/orders/{id}/cancelcancel a pending order

Errors: 409 already_owned, 409 not_for_sale, and 409 insufficient_funds with missing and missingUsd.

bash
curl -s https://api.0x.limo/v1/store/orders -H "Authorization: Bearer $TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" -H 'Content-Type: application/json' -d '{"appid": 4000011}'

A paid game's hosted site is built origin-only: no swarm, so nothing of it is shared player to player. Its gate, which lets only owners in, uses play tickets.

#Play tickets

A play ticket is a short-lived proof, signed by 0x, that a player may play a game on a given site origin:

text
ticket  = b64url(payload) "." b64url(HMAC-SHA256(secret, b64url(payload)))
payload = {"a": <appid>, "o": "<site origin>", "s": "<steamid>", "e": <expiry, unix s>, "j": "<nonce>"}
  • POST /v1/apps/{appid}/play-ticket → {ticket, appid, origin, expires_in, paid}. A paid game gives tickets only to owners; others get 402 {"error": "not_owned", "price": {...}}.
  • POST /v1/play-tickets/verify {ticket} (public) → {valid, appid, origin, steamid, expires}, for a server that doesn't hold the secret.

Not enabled on 0x.limo yet

The ticket signing key isn't configured on 0x.limo, so POST /v1/apps/{appid}/play-ticket answers 503 play_tickets_closed.

#Developer revenue and payouts

The platform fee is 10% of each sale. The rest is yours.

RouteDoes
GET /v1/dev/revenue{fee_percent, currencies: [{currency, gross_sales, refunds, platform_fees, earned, available, payouts_pending, paid_out}], games, recent_sales, payouts, settlement} (minor units)
GET /v1/dev/payout-accountyour USDT payout addresses and preferred network
PUT /v1/dev/payout-account {addresses, payout_network?}set or change addresses per network (0x… EIP-55 for EVM networks, T… for Tron; null removes one)
bashtested
curl -s https://api.0x.limo/v1/dev/revenue -H "Authorization: Bearer $ZEROX_TOKEN"

Payouts go to the address of your preferred network. The /dev/submit portal has the same views.

#In-game purchases

Switched off on 0x.limo

In-game purchases are built and tested but switched off on 0x.limo. Every route below answers 404 {"error": "in-game purchases are off"} until they go live.

The design: your game asks the launcher to sell an item, the player confirms in the launcher's own dialog, the price comes off the 0x balance, and your game server checks a signed receipt.

WhoRouteDoes
DeveloperPUT /v1/dev/apps/{appid}/iap/items/{sku}add or change an item {name, description?, price, kind: consumable | permanent, max_per_player?, active?}
DeveloperPOST /v1/dev/apps/{appid}/iap/server-keya server key 0xsk_<appid>_... for your game servers (shown once)
GameGET /v1/apps/{appid}/iap/itemsitems on sale with what the player owns and their balance
GamePOST /v1/apps/{appid}/iap/intents {sku, quantity?}ask to buy → a pending intent the player confirms in the launcher
ServerPOST /v1/iap/server/verify {receipt}check a receipt (Bearer: the server key)
ServerPOST /v1/iap/server/consume {purchase, quantity?, idempotency_key?}use up a consumable
ServerGET /v1/iap/server/players/{steamid}/inventorya player's items of your app
AnyoneGET /v1/iap/keysthe Ed25519 keys receipts are signed with

Receipts look like x1r1.<b64url(payload)>.<b64url(sig)>. The signature is over the ASCII bytes "x1-iap-receipt-v1." + b64url(payload), so a server can verify one offline. The @0xlimo/iap package wraps all of this.

#Subscriptions

Switched off on 0x.limo

Subscriptions are built and tested but switched off on 0x.limo. Every route below answers 404 {"error": "subscriptions are off"} until they go live.

The design: a game has plans. Each plan has an entitlement key your game checks and prices per week, month or year. Subscribers pay each period from the 0x balance. A game can be subscription-only, which makes an active subscription count as owning it.

WhoRouteDoes
DeveloperPOST /v1/dev/apps/{appid}/plansadd a plan {name, description?, entitlement, prices: {month, week?, year?}}
DeveloperPUT /v1/dev/apps/{appid}/plans/{id}edit or retire a plan (the entitlement key never changes)
DeveloperPUT /v1/dev/apps/{appid}/subscription {only}subscription-only on or off
DeveloperGET /v1/dev/subscriptionsyour plans with subscriber counts
PlayerPOST /v1/me/subscriptions {plan, period}subscribe, first period paid at once
PlayerPOST /v1/me/subscriptions/{id}/cancel / .../resumecancel at period end / undo or pay an overdue renewal
GameGET /v1/me/apps/{appid}/subscriptionwhat the player holds for this game
ServerGET /v1/gameservers/entitlement/{steamid}/{key}game-server session: does the player hold the key now
ServerPOST /v1/subscriptions/check {ticket, entitlement?}hosted servers: check a player's play ticket and entitlements

See the generated me reference and apps reference.