Raw API

Register a user

Trusted registration returns a persistent user_code. You own the user's UX and OTP; we never message them.

curl -X POST https://api.oropocket.com/partner/users/init \
  -H "Authorization: Bearer oro_live_xxx" \
  -d '{"flow":"api","mobile":"9000000001","name":"Anya"}'

Buy

Two steps — quote, then confirm. Quotes lock a price for a short window.

# quote → returns quote_id + grams + rate
curl -X POST https://api.oropocket.com/partner/buy/quote \
  -H "Authorization: Bearer oro_live_xxx" \
  -d '{"user_code":"usr_xxx","asset_type":"gold","amount_inr":1000}'

# confirm
curl -X POST https://api.oropocket.com/partner/buy/confirm \
  -H "Authorization: Bearer oro_live_xxx" \
  -H "Idempotency-Key: <uuid>" \
  -d '{"quote_id":"tqt_xxx"}'

Merchant markup (Pro)

On the Pro plan you set your own spread on our rates — added to buy, taken off sell. Your users are quoted the marked-up price, your wallet is debited the full marked-up amount on a buy, your user is credited the reduced amount on a sell, and the difference comes back to you on your monthly statement — Billing works the money through end to end. The same pair of percentages also prices the hosted checkout and anything you render from GET /partner/prices, so there is one number to keep straight, not three. Here is how to set it.

No capability needed — unlike every other endpoint on this page, the two markup calls are authorised by your token alone, so they work whatever your allowed_apis grants are.

Reading it returns your current setting and whether your plan allows one:

Setting it takes either field, or both. A field you omit is left alone, so you can change one side without reading the other first:

# read
curl https://api.oropocket.com/partner/dashboard/markup \
  -H "Authorization: Bearer oro_live_xxx"

# 2% on buys, 1% on sells
curl -X PUT https://api.oropocket.com/partner/dashboard/markup \
  -H "Authorization: Bearer oro_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"markup_buy_pct": 2, "markup_sell_pct": 1}'

# change only the sell side
curl -X PUT https://api.oropocket.com/partner/dashboard/markup \
  -H "Authorization: Bearer oro_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"markup_sell_pct": 0.5}'

Unlike the read, this one refuses rather than silently storing something else:

What changes on a buy quote. Once a markup is in effect, POST /partner/buy/quote carries three extra fields. When it isn't — the default, and every free-tier partner — the response is exactly as documented above, with no extra fields at all, so an existing integration sees no change until you set one.

Sell

Sell mirrors buy — quote then confirm. Proceeds settle into the end user's INR wallet, not your float.

A sell markdown never comes out of amount_inr. Ask for ₹15,000 with a 2% markdown and your user is credited ₹15,000 — we sell about 2% more metal and hand you the difference. It is the mirror of the buy side, where a fixed rupee amount buys your user slightly less metal. quantity_grams quotes are unaffected: there the markdown reduces the payout, because the quantity is fixed.

Users, portfolio & balances

Lists the users you registered. Add ?include=balances for a per-user holdings snapshot, and ?scope=all to also include embed-verified and attributed users (each row then carries a sources array). Paginate with limit (1–200) and offset.

One user's detail. Identity is deliberately masked — you address users only by user_code.

Holdings for one user. Values are scoped to your sub-wallet, not the user's whole OroPocket balance — read sub-wallets before you reconcile against these numbers.

curl "https://api.oropocket.com/partner/users?include=balances" \
  -H "Authorization: Bearer oro_live_xxx"

curl "https://api.oropocket.com/partner/users/usr_xxx?include=balances" \
  -H "Authorization: Bearer oro_live_xxx"

Users must complete KYC before they can withdraw. Configure webhooks to get settlement events.