For developers

API for partners.

REST API for partners. Single Bearer key, idempotent requests, JSON in/out — zero ceremony.

Open Swagger Get a key

BASE URL

https://api.theopenmoney.info/api/v1

Auth

Authorization: Bearer

Format

REST · JSON

Quickstart

Three steps to your first order.

Step 01

Get a key

DM the bot /api — it returns a key (osk_…). Keep it secret.

Step 02

Send a request

POST /orders/stars with a recipient and amount.

Step 03

Take the result

Response has order_id, payment address, memo and TTL.

POST /orders/stars

curl -X POST https://api.theopenmoney.info/api/v1/orders/stars \
  -H "Authorization: Bearer $KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "recipient_username": "pandus",
    "quantity": 100,
    "payment_method": "ton_memo",
    "payment_currency": "TON",
    "client_reference": "invoice-42"
  }'

200 OK · JSON response

{
  "ok": true,
  "data": {
    "id": 10421,
    "status": "pending_payment",
    "order_type": "stars",
    "stars_amount": 100,
    "recipient_username": "pandus",
    "price_ton": 0.418,
    "payment_address": "UQBFJTkJ5hZdH7i6rWQTnm43zn6h2dPBV9lFZ2e98WvWABy_",
    "payment_memo": "STARS-a1b2c3",
    "expires_at": "2026-04-16T12:15:00Z",
    "created_at": "2026-04-16T12:00:00Z"
  }
}

Auth

One header.

Every request authenticates via the Authorization: Bearer osk_… header. One key = one partner and one TON top-up address.

Never put the key in client-side code or URLs.
Rate limits are enforced per key.
Leaked? Revoke it and request a new one from the bot.

HTTP request

GET /api/v1/balance HTTP/1.1
Host: api.theopenmoney.info
Authorization: Bearer osk_••••••••••••••••
Accept: application/json

Endpoints

Every route.

In Swagger

Orders

POST/orders/starsCreate a Stars order
POST/orders/premiumCreate a Premium order (3 / 6 / 12 months)
GET/orders/{id}Get order by ID
GET/ordersList orders
GET/orders/by-memo/{memo}Find order by payment_memo
GET/orders/by-reference/{ref}Find orders by your client_reference
GET/orders/stats/summaryAggregate stats
POST/orders/{id}/cancelCancel a pending_payment order

Pricing

GET/pricing/ton-rateCurrent TON/USD rate
GET/pricing/feeService fees and min/max limits
GET/pricing/estimate/starsEstimate Stars price in TON
GET/pricing/estimate/premiumEstimate Premium price in TON

Recipients

GET/recipients/starsCheck if a username can receive Stars
GET/recipients/premiumCheck if a username can receive Premium

Balance

GET/balancePartner balance and top-up address
GET/balance/transactionsBalance transactions history

Health

GET/healthService health probe

Examples

curl recipes.

Create a Stars order

POST /orders/stars

curl -X POST https://api.theopenmoney.info/api/v1/orders/stars \
  -H "Authorization: Bearer $KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "recipient_username": "pandus",
    "quantity": 100,
    "payment_method": "ton_memo",
    "payment_currency": "TON",
    "client_reference": "invoice-42"
  }'

Poll order status

GET /orders/{id}

curl https://api.theopenmoney.info/api/v1/orders/10421 \
  -H "Authorization: Bearer $KEY"

Check a recipient

GET /recipients/stars

curl "https://api.theopenmoney.info/api/v1/recipients/stars?username=pandus" \
  -H "Authorization: Bearer $KEY"

Estimate price

GET /pricing/estimate/stars

curl "https://api.theopenmoney.info/api/v1/pricing/estimate/stars?quantity=100" \
  -H "Authorization: Bearer $KEY"

Reliability

Retry-safe by design.

Idempotency-Key

Pass any UUID in the Idempotency-Key header — a retry with the same key returns the same order instead of creating a new one. Essential for handling timeouts and retries.

Header

Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000

client_reference

Optionally attach your own ID (invoice number, payment_id) when creating an order. Later look it up: GET /orders/by-reference/{ref} returns all matching orders.

Body field

{
  "client_reference": "invoice-42"
}

One format.

Every error follows the same shape: ok=false with a machine-readable error_code and human-readable error_message.

Common codes

401: Missing or invalid Bearer token
404: Resource not found (or doesn't belong to your key)
409: State conflict — e.g. cannot cancel a paid order
422: Invalid request parameters
429: Rate limit exceeded

Error response

{
  "ok": false,
  "error_code": "VALIDATION_ERROR",
  "error_message": "quantity must be between 50 and 10000",
  "data": null
}

Ready toship?

Full interactive schema lives in Swagger. Your key is one bot command away.

Swagger Get a key