RubikTrade-For Beginners is RubikTrade's Android trading app for first-time short-duration traders. Users choose a country, sign in with email and password or Google/Facebook, then buy or sell foreign-exchange, commodity and index instruments on a timed candlestick screen. A live wallet sits alongside a resettable demo wallet for practice. Its markets include India, Brazil, Indonesia, Pakistan, Nigeria, the Philippines, Thailand and Mexico. Funding options vary by country, including UPI and Paytm in India, Pix and Boleto in Brazil, CLABE in Mexico and OVO in Indonesia; local bank and wallet payouts follow identity verification. The app serves the emerging-market retail trading audience also addressed by Olymptrade and IQ Option.
Timed-ticket outcomes link positionId, openPrice and closePrice to settleTimestamp, resultAmount and grossProfit. Quote candles supply cp, ct and the OHLC fields o, h, l and c for each symbol, allowing a ticket blotter to align price windows with entry, expiry and settlement.
Wallet records distinguish cash balance, bonus and totalAmount from the practice simulation wallet, with userId and currencyType providing account and currency context. Funding records carry orderNo, realAmount, serviceFee and rail-specific references such as clabe. A reconciliation service can match credited deposits and net payouts without mixing them with demo resets, while a permissioned payout queue can check userStatus, isActivate and maxWithdrawAmount before releasing funds. openData Studio turns these ticket, wallet and funding records into callable open data for bookkeeping, trade-history views and payout controls.
Screenshots
API surface
The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.
Email login
POST
/v1/trader-access/email-sessionosintSigns the trader in with email and password. Returned token, userId and accountNumber support subsequent authenticated requests; serverUrl and localHostUrl carry regional service settings.
Auth: Unauthenticated email/password sign-in. JSON body includes source=email, deviceId and gaid. Google/Facebook sign-in variants use the same session model. A device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request.
- password
- source
- deviceId
- gaid
- token
- userId
- accountNumber
- country
- currency
- currencyType
- language
- isVerifyed
- simulationAmount
- userLevel
- serverUrl
- localHostUrl
- registTimestamp
POST /v1/trader-access/email-session HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "email": "[email protected]", "password": "<password>", "source": "email", "deviceId": "<device-id>", "gaid": "<advertising-id>", "os": "android" }{ "status": 0, "code": "0000", "message": "OK", "data": { "token": "<session-token>", "userId": 700001, "accountNumber": "DEMO-700001", "email": "[email protected]", "name": "Example Trader", "phone": "<phone-number>", "country": "INDIA", "currency": "rupee", "currencyType": "INR", "language": "en", "isVerifyed": "1", "isSimulation": false, "simulationAmount": "10000", "userLevel": "1", "source": "email", "deviceId": "<device-id>", "serverUrl": "<regional-service-url>", "localHostUrl": "<regional-service-url>", "registTimestamp": 1710230400000 } }Live wallet balance
POST
/v1/wallets/cash/snapshotopenbankingReads the live wallet shown on the home cash tile, including cash balance, bonus, totalAmount and currencyType.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Regional service selection follows the session settings.
- userId
- token
- source
- balance
- bonus
- simulation
- totalAmount
- currencyType
- currencySymbol
- resetSuccess
POST /v1/wallets/cash/snapshot HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "source": "home" }{ "status": 0, "code": "0000", "data": { "userId": "700001", "balance": "15240.50", "bonus": "500.00", "simulation": "0", "totalAmount": "15740.50", "currencyType": "INR", "currencySymbol": "₹", "resetSuccess": 0 } }Simulation wallet balance
POST
/v1/wallets/practice/snapshotopenfinanceReads the demo wallet used in simulation mode. resetSuccess indicates whether the starting practice balance was restored.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. The practice-wallet flow also supports restoring the starting amount.
- userId
- balance
- bonus
- simulation
- totalAmount
- resetSuccess
- currencyType
POST /v1/wallets/practice/snapshot HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "source": "demo" }{ "status": 0, "code": "0000", "data": { "userId": "700001", "balance": "10000.00", "bonus": "0", "simulation": "1", "totalAmount": "10000.00", "currencyType": "INR", "currencySymbol": "₹", "resetSuccess": 0 } }Instrument catalog
POST
/v1/markets/catalogopendataReturns grouped tradeable instruments with payout percent in profit, live/demo stake limits and the settleType used by timed tickets.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Related catalog flows provide instrument details.
- productType
- productIds
- symbol
- showSymbol
- name
- productId
- currentPrice
- changeRate
- profit
- min
- max
- amount
- demoMin
- demoMax
- exchangeName
- settleType
- isLimited
- accuracy
POST /v1/markets/catalog HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>" }{ "status": 0, "code": "0000", "data": { "productData": [ { "productType": "FX", "productIds": [ "EURUSD", "GBPUSD" ], "productList": [ { "symbol": "EURUSD", "showSymbol": "EUR/USD", "name": "Example Trader", "productId": "1001", "productType": "FX", "currentPrice": "1.08742", "changeRate": "0.12", "profit": "85", "min": "10", "max": "5000", "amount": "100", "demoMin": "10", "demoMax": "1000", "demoAmount": "50", "exchangeName": "OTC", "platformName": "RubikTrade", "settleType": "time", "isLimited": "00", "accuracy": 5 } ] } ] } }Quote candles
POST
/v1/markets/candlesopendataReturns OHLC candles for a symbol, including last close cp at tick time ct, open o, high h, low l, close c and the st/et window shown on the chart.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Regional streaming updates supplement the candle history.
- symbol
- lineType
- productId
- positionId
- quotationList
- cp
- ct
- o
- h
- l
- c
- st
- et
POST /v1/markets/candles HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "symbol": "EURUSD", "lineType": "1" }{ "status": 0, "code": "0000", "data": { "symbol": "EURUSD", "productId": "1001", "lineType": "1", "positionId": 0, "quotationList": [ { "symbol": "EURUSD", "productId": "1001", "cp": "1.08742", "ct": 1710230460123, "o": "1.08610", "h": "1.08910", "l": "1.08480", "c": "1.08742", "st": 1710230400000, "et": 1710230460000 } ] } }Submit timed ticket
POST
/v1/tickets/createopenfinancePlaces a timed buy/sell ticket against the current quote and returns positionId, openPrice and the settleTimestamp at which the ticket expires.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Practice mode supports the equivalent ticket submission.
- symbol
- amount
- buySell
- productId
- timeUnit
- timeUnitType
- positionId
- openPrice
- closePrice
- openCost
- openCharge
- openPositionTimestamp
- settleTimestamp
- endTime
- result
- resultAmount
- grossProfit
- bonusAmount
- currencyType
POST /v1/tickets/create HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "symbol": "EURUSD", "amount": 100.0, "buySell": 1, "productId": "1001", "timeUnit": 60, "timeUnitType": "S" }{ "status": 0, "code": "0000", "data": { "id": 88004567, "positionId": 88004567, "symbol": "EURUSD", "name": "Example Trader", "code": "EURUSD", "buySell": 1, "amount": 100.0, "openPrice": "1.08742", "closePrice": "0", "openCost": 100.0, "openCharge": 0.0, "timeUnit": 60, "timeUnitType": "S", "openPositionTimestamp": 1710230461000, "settleTimestamp": 1710230521000, "endTime": 1710230521, "result": 0, "resultAmount": "0", "grossProfit": "0", "bonusAmount": "0", "productId": "1001", "currencyType": "INR" } }Open (unliquidated) tickets
POST
/v1/tickets/runningopenfinanceLists live tickets still running, with openPrice, settleTimestamp and isRunning for the countdown display associated with each positionId.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Practice mode maintains an equivalent running-ticket list.
- positionId
- symbol
- buySell
- amount
- openPrice
- closePrice
- timeUnit
- timeUnitType
- openPositionTimestamp
- settleTimestamp
- endTime
- result
- grossProfit
- isDeferred
- isRunning
POST /v1/tickets/running HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>" }{ "status": 0, "code": "0000", "data": [ { "positionId": 88004567, "symbol": "EURUSD", "name": "Example Trader", "buySell": 1, "amount": 100.0, "openPrice": "1.08742", "closePrice": "0", "timeUnit": 60, "timeUnitType": "S", "openPositionTimestamp": 1710230461000, "settleTimestamp": 1710230521000, "endTime": 1710230521, "result": 0, "grossProfit": "0", "productId": "1001", "isDeferred": false, "isRunning": true } ] }Settled ticket history
POST
/v1/tickets/settledopenfinancePages settled tickets with openPrice versus closePrice, win/loss result, resultAmount and grossProfit after settleTimestamp.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Practice mode maintains an equivalent settled-ticket list.
- positionId
- symbol
- buySell
- amount
- openPrice
- closePrice
- result
- resultAmount
- grossProfit
- timeUnit
- openPositionTimestamp
- closePositionTimestamp
- settleTimestamp
- bonusAmount
- currencyType
POST /v1/tickets/settled HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>" }{ "status": 0, "code": "0000", "data": [ { "positionId": 88004510, "symbol": "EURUSD", "name": "Example Trader", "buySell": 1, "amount": 100.0, "openPrice": "1.08690", "closePrice": "1.08755", "result": 1, "resultAmount": "185.00", "grossProfit": "85.00", "timeUnit": 60, "timeUnitType": "S", "openPositionTimestamp": 1710226801000, "closePositionTimestamp": 1710226861000, "settleTimestamp": 1710226861000, "bonusAmount": "0", "currencyType": "INR" } ] }Deposit amount ladder
POST
/v1/funding/presetsopenbankingReturns preset deposit amounts and the bonusFixed / bonusRatio values shown with funding offers.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request.
- country
- activity
- amount
- bonus
- bonusAmount
- bonusFixed
- bonusRatio
- defaultChoose
- selectFlag
- isActiveAmount
POST /v1/funding/presets HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>" }{ "status": 0, "code": "0000", "data": { "country": "INDIA", "activity": 1, "amountModelBeanList": [ { "amount": "2000", "bonus": "100", "bonusAmount": "100", "bonusFixed": "100", "bonusRatio": "0.05", "defaultChoose": "1", "selectFlag": "0", "isActiveAmount": true } ] } }Create deposit order
POST
/v1/funding/orders/createopenbankingOpens a funding order for UPI/Paytm in India, Pix/Boleto in Brazil or CLABE in Mexico. Returns orderNo and rail-specific values such as txnToken, qrCode, barcode or clabe.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Funding uses the session-selected regional service.
- amount
- channel
- payModel
- orderNo
- orderid
- executeAmount
- executeCurrency
- txnToken
- qrCode
- clabe
- barcode
- webUrl
- expireTime
- minAmount
- maxAmount
- otpFlag
POST /v1/funding/orders/create HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "amount": "2000", "channel": "UPI", "payModel": "PAYTM" }{ "status": 0, "code": "0000", "data": { "orderNo": "D20261026001", "orderid": "D20261026001", "amount": "2000", "executeAmount": "2000", "executeCurrency": "INR", "channel": "UPI", "payModel": "PAYTM", "txnToken": "<payment-token>", "qrCode": "<payment-qr-payload>", "clabe": "", "barcode": "", "webUrl": "<checkout-link>", "expireTime": "1710231600000", "minAmount": "500", "maxAmount": "50000", "otpFlag": "0" } }Request withdrawal
POST
/v1/payouts/requestopenbankingSubmits a payout to a saved IFSC bank, Paytm, Pix or wallet collection account. The response separates executeApplyAmount, serviceFee, realAmount and lockAmount.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. A separate payout preview can estimate the fees before submission.
- amount
- collectionAccountId
- collectionAccountType
- realAmount
- executeAmount
- executeApplyAmount
- executeCurrency
- currencyType
- serviceFee
- bonusAmount
- lockAmount
- maxWithdrawAmount
- exchangeRate
- warnFlag
POST /v1/payouts/request HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "amount": "1500", "collectionAccountId": "55001", "collectionAccountType": "BANK" }{ "status": 0, "code": "0000", "data": { "realAmount": "1470", "executeAmount": "1470", "executeApplyAmount": "1500", "executeCurrency": "INR", "currencyType": "INR", "serviceFee": "30", "bonusAmount": "0", "lockAmount": "0", "maxWithdrawAmount": "15240.50", "exchangeRate": "1", "warnFlag": "0" } }Deposit and withdrawal ledger
POST
/v1/cash/movementsopenbankingPages deposit and withdrawal ledger rows filtered by orderType, including Paytm numbers where that rail was used. Related order details include Pix keys, IFSC codes and bank names.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request.
- orderType
- orderNo
- orderStatus
- applyAmount
- realAmount
- serviceFee
- paytmName
- paytmNo
- applyTime
- confirmTime
- reviewDesc
POST /v1/cash/movements HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>", "orderType": "01" }{ "status": 0, "code": "0000", "data": [ { "orderNo": "D20261026001", "orderStatus": "02", "orderType": "01", "applyAmount": 2000.0, "realAmount": 2000.0, "serviceFee": 0.0, "paytmName": "Example Trader", "paytmNo": "<wallet-number>", "applyTime": "2026-10-26 09:10:00", "confirmTime": "2026-10-26 09:12:11", "reviewDesc": "credited" } ] }KYC snapshot
POST
/v1/identity/statusosintReturns an India identity-verification snapshot with Aadhaar head number, PAN number and image reference, plus userStatus used to gate deposits and withdrawals.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request. Related identity flows provide verification status.
- userStatus
- enforcePanImg
- payOrder
- prompt
- name
- mobile
- aadHeadNumber
- panNum
- panImg
POST /v1/identity/status HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>" }{ "status": 0, "code": "0000", "data": { "userStatus": "1", "enforcePanImg": false, "payOrder": true, "prompt": false, "kycInfo": { "id": 4412, "name": "Example Trader", "mobile": "<phone-number>", "aadHeadNumber": "XXXX-XXXX-0000", "userStatus": "1" }, "kycPanInfo": { "id": 4412, "userId": 700001, "panNum": "<pan-number>", "panImg": "<document-image-url>" } } }Payout collection account
POST
/v1/payouts/destinationsopenbankingReads the saved payout destination: IFSC bank fields for India, a Paytm/OVO wallet channel or a Pix-capable collection account, together with isActivate.
Auth: Session token returned by sign-in, supplied in the JSON body as token with userId. Device cookie yh=<device-hash> and X-Amzn-Trace-Id accompany the request.
- accountTypeSort
- collectionAccountId
- collectionAccountType
- bankName
- bankCode
- bankAccountNumber
- holderName
- documentId
- documentType
- mobile
- currencyType
- withdrawChannel
- withdrawChannelName
- isActivate
POST /v1/payouts/destinations HTTP/1.1 Content-Type: application/json Cookie: yh=<device-hash> X-Amzn-Trace-Id: <trace-id> { "userId": 700001, "token": "<session-token>" }{ "status": 0, "code": "0000", "data": { "accountTypeSort": "BANK", "isSelection": "1", "isShowBank": true, "isNoDeposit": false, "bankAccount": { "collectionAccountId": "55001", "collectionAccountType": "BANK", "bankName": "HDFC Bank", "bankCode": "HDFC", "bankAccountNumber": "<bank-account-number>", "holderName": "Example Trader", "documentId": "<identity-number>", "documentType": "PAN", "mobile": "<phone-number>", "currencyType": "INR", "withdrawChannel": "IFSC", "isActivate": true, "userId": "700001" }, "walletAccount": { "collectionAccountId": "55002", "collectionAccountType": "WALLET", "holderName": "Example Trader", "withdrawChannel": "PAYTM", "withdrawChannelName": "Paytm", "isActivate": true } } }
Data categories
- balances
- quotes
- orders
- deposits
- withdrawals
- kyc
- instruments
Where teams use this data
Live vs demo wallet reconciliation
A bookkeeping bot pulls live balance, bonus and totalAmount from the cash tile, the parallel simulation wallet, then matches settled tickets on resultAmount and grossProfit so demo resets never mix with INR/BRL/MXN cash.
Timed-ticket blotter
A desk overlay joins quote-candle cp/o/h/l for a symbol with open unliquidated rows (openPrice, settleTimestamp, buySell, isRunning) and pages history once result and closePrice land.
KYC gate before IFSC, Pix or CLABE payout
A withdrawals queue reads userStatus, aadHeadNumber and panNum, then only releases a withdraw row when the collection account's bankAccountNumber or withdrawChannel is active and maxWithdrawAmount covers executeApplyAmount plus serviceFee.
Multi-rail funding tracker
Treasury maps deposit orderNo, channel, txnToken, qrCode, clabe and barcode against capital-list rows (realAmount, paytmNo, reviewDesc) to see which UPI, Pix, Boleto and CLABE rails actually credited.
Frequently asked questions
What quote fields do the RubikTrade examples cover?
The illustrative candle response includes symbol, last close cp, tick time ct, open o, high h, low l, close c and window boundaries st/et. The instrument catalog adds profit as the payout percentage, min/max stake, demoMin/demoMax and settleType per productId.
How are timed tickets represented?
A submission carries symbol, amount, buySell, productId, timeUnit and timeUnitType. Running tickets expose positionId, openPrice, settleTimestamp and isRunning. Settled history adds closePrice, result, resultAmount and grossProfit so the two stages can be joined without treating an open position as a completed outcome.
Which funding rails appear in the cash records?
India funding includes UPI/Paytm values such as txnToken, qrCode and paytmNo; Brazil uses Pix/Boleto, including barcode, and Mexico uses clabe. Ledger rows carry orderNo, applyAmount, realAmount, serviceFee and reviewDesc. Withdrawal results separate executeApplyAmount, serviceFee, realAmount and lockAmount. Payment instructions and account values shown here are placeholders.
How is authentication shown in the illustrative requests?
Email sign-in is unauthenticated and returns token, userId and accountNumber. Later examples carry the session token and userId in the JSON body, together with a device cookie and a tracing header. Tokens and device values are placeholders; the displayed paths are illustrative and do not identify a live service.
Apps similar to RubikTrade-For Beginners
- Olymptrade – Trading online — Olymptrade is an online trading app for forex, stocks and other assets, with chart indicators and a free demo account that uses live market quotes without putting cash at risk.
- IQ Option – Trading Platform — IQ Option is a mobile platform for trading CFDs on stocks, forex and crypto as well as 200+ assets such as indices, commodities and shares, with a reloadable demo account that can be switched to a live book.
- Guru Trade7-Serving 7 Years — GuruTrade7 is an online trading platform with 200+ assets, real-time quotes and a demo account of virtual funds for practicing before live trades.
- Marketly Assistant by Binomo — Marketly Assistant is the Android client powered by the Binomo short-term trading platform, with chart drawings, educational material and a demo account for practicing before live trading.
- Exness Trade: Online Trading — Exness Trade is a mobile app for trading stocks, gold and other markets, with a free demo account and an in-app terminal for watchlists, balances and orders.
- MetaTrader 5 — Forex, Stocks — MetaTrader 5 is a forex and stock trading terminal with real-time quotes, charts, technical analysis, news and free demo accounts.
- TradingView: Track All Markets — TradingView is a charting and trading app for stocks, forex and crypto, with professional charts, watchlists, alerts and paper trading with virtual funds.
Topics
- rubiktrade data api
- rubiktrade quote candles
- timed ticket settlement data
- live and demo wallet records
- upi pix clabe funding data
- payout verification status
Need this app's data API integrated?
We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.
- NDA + SOW on every engagement
- Delivery in 3–7 days
- Payment only after acceptance
- Work scoped to authorized use