Guru Trade7-Serving 7 Years icon

GuruTrade7 quotes, tickets and KYC data API

GuruTrade7 · Banking

Guru Trade7-Serving 7 Years is GuruTrade7's Android app for short-duration trading, with candlestick charts, FX, commodity and index instruments, timed buy/sell tickets and one-click stake sizing. Traders can sign in with email and password or Google/Facebook and switch between a live wallet and a resettable practice wallet. Its India-facing funding features include UPI, Paytm and Cashfree, with PAN and Aadhaar verification and IFSC bank payouts; Brazil-facing features include Pix funding and payouts, CPF-linked collection accounts and a dedicated Brazil Telegram channel. The app serves retail traders in India and Brazil alongside other short-term trading terminals such as Olymptrade and IQ Option.

Timed-ticket settlements connect openPrice, closePrice and resultAmount to a symbol, a buySell direction and a settleTimestamp. Alongside those positions, quote records provide the ticker sb, last price cp, tick time ct, percentage change pchg and session highs and lows. Instrument records add profit, min, max and settleType, allowing a ticket blotter to pair position outcomes with the displayed quote and stake limits.

Wallet snapshots keep balance and bonus alongside the simulation flag, so bookkeeping tools can separate practice activity from real-money movements. Funding records link orderNo to payType, applyAmount, realAmount and currencyType; payout records add serviceFee and a bank or Pix destination. Identity and destination records contribute userStatus, aadHeadNumber, panNum, pixKey, ifscCode and withDrawableValue for authorized payout-readiness checks. These fields support wallet reconciliation, timed-ticket reporting and UPI/Pix funding trackers; openData Studio turns them into callable open data.

Screenshots

  • Guru Trade7-Serving 7 Years screenshot 1
  • Guru Trade7-Serving 7 Years screenshot 2
  • Guru Trade7-Serving 7 Years screenshot 3
  • Guru Trade7-Serving 7 Years screenshot 4
  • Guru Trade7-Serving 7 Years screenshot 5

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/sessions/start osint

    Signs the trader in with email and password. The returned access_token, userId and accountNumber are copied onto later JSON bodies as token / userId.

    Auth: Unauthenticated. Email sign-in sends email, password and source=email in the JSON body, together with device identifiers aid and gaid. Social sign-in variants use access_token or googleSecretToken instead of the password.

    • email
    • password
    • source
    • access_token
    • userId
    • accountNumber
    • country
    • language
    • isVerifyed
    • bonusAmount
    • simulationAmount
    • registTimestamp
    POST /v1/sessions/start HTTP/1.1
    Content-Type: application/json
    
    {
      "email": "[email protected]",
      "password": "<password>",
      "source": "email",
      "aid": "<android-id>",
      "gaid": "<advertising-id>",
      "appSource": "GP",
      "pName": "com.gurutrade7.app",
      "os": "android",
      "terminal": "android"
    }
    {
      "respCode": "0000",
      "respMessage": "OK",
      "data": {
        "access_token": "<session-token>",
        "userId": "<user-id>",
        "accountNumber": "<account-number>",
        "email": "[email protected]",
        "name": "<account-holder>",
        "country": "IN",
        "language": "en",
        "isVerifyed": "1",
        "bonusAmount": "0",
        "simulationAmount": "10000",
        "registTimestamp": 1710230400000,
        "source": "email"
      }
    }
  • Live wallet balance

    POST /v1/wallets/live/snapshot openbanking

    Reads the live wallet: cash balance, bonus bucket and the simulation flag used by the home cash tile.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body; appSource=GP and os=android supply client context.

    • userId
    • token
    • source
    • balance
    • bonus
    • simulation
    • resetSuccess
    POST /v1/wallets/live/snapshot HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "source": "home",
      "appSource": "GP",
      "os": "android"
    }
    {
      "respCode": "0000",
      "data": {
        "userId": "<user-id>",
        "balance": "15240.50",
        "bonus": "500.00",
        "simulation": "0",
        "resetSuccess": 0
      }
    }
  • Simulation wallet balance

    POST /v1/wallets/practice/snapshot openfinance

    Reads the demo wallet shown when the trader toggles simulation mode. A sister reset call restores the starting simulation amount.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • userId
    • balance
    • bonus
    • simulation
    • resetSuccess
    POST /v1/wallets/practice/snapshot HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "source": "demo"
    }
    {
      "respCode": "0000",
      "data": {
        "userId": "<user-id>",
        "balance": "10000.00",
        "bonus": "0",
        "simulation": "1",
        "resetSuccess": 0
      }
    }
  • Instrument catalog

    POST /v1/markets/catalog/query opendata

    Returns grouped tradeable instruments with payout percent (profit), live/demo stake limits and the settleType that drives the timed ticket pad.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body alongside useType; interfaceVersion=3.0 selects the version-three instrument list.

    • useType
    • interfaceVersion
    • productType
    • productIds
    • symbol
    • showSymbol
    • name
    • productId
    • currentPrice
    • profit
    • min
    • max
    • exchangeName
    • settleType
    • isLimited
    POST /v1/markets/catalog/query HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "useType": "1",
      "interfaceVersion": "3.0"
    }
    {
      "respCode": "0000",
      "data": [
        {
          "productType": "FX",
          "productIds": [
            "EURUSD",
            "GBPUSD"
          ],
          "productList": [
            {
              "symbol": "EURUSD",
              "showSymbol": "EUR/USD",
              "name": "Euro vs US Dollar",
              "productId": "1001",
              "productType": "FX",
              "currentPrice": "1.08742",
              "profit": 85.0,
              "min": 10.0,
              "max": 5000.0,
              "exchangeName": "OTC",
              "settleType": "time",
              "isLimited": "00",
              "demoMin": 10.0,
              "demoMax": 1000.0
            }
          ]
        }
      ]
    }
  • Last quote tick

    POST /v1/markets/quotes/latest opendata

    Returns the last tick for one symbol: last price cp, percent change pchg, session high/low and the ticker code sb used on the chart.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body alongside symbol.

    • symbol
    • sb
    • showSymbol
    • cp
    • ct
    • pchg
    • change
    • highPrice
    • lowPrice
    • openingTodayPrice
    • closedYesterdayPrice
    • exchangeName
    • sysTime
    • upDown
    POST /v1/markets/quotes/latest HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "symbol": "EURUSD"
    }
    {
      "respCode": "0000",
      "data": {
        "sb": "EURUSD",
        "showSymbol": "EUR/USD",
        "cp": 1.08742,
        "ct": 1710230460123,
        "pchg": 0.12,
        "change": 0.0013,
        "highPrice": 1.0891,
        "lowPrice": 1.0848,
        "openingTodayPrice": 1.0861,
        "closedYesterdayPrice": 1.08612,
        "exchangeName": "OTC",
        "platformName": "GuruTrade7",
        "sysTime": 1710230460500,
        "upDown": 1.0,
        "goodType": "FX"
      }
    }
  • Submit timed ticket

    POST /v1/tickets/create openfinance

    Places a timed buy/sell ticket against the current quote. Response returns positionId, openPrice and the settleTimestamp when the ticket expires.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • symbol
    • amount
    • buySell
    • profit
    • timeUnit
    • timeUnitType
    • quotationTime
    • oneClick
    • positionId
    • openPrice
    • closePrice
    • openPositionTimestamp
    • settleTimestamp
    • result
    • resultAmount
    • grossProfit
    POST /v1/tickets/create HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "symbol": "EURUSD",
      "amount": "100",
      "buySell": "1",
      "profit": "85",
      "timeUnit": 60,
      "timeUnitType": "S",
      "quotationTime": 1710230460123,
      "oneClick": 0,
      "guide": "0"
    }
    {
      "respCode": "0000",
      "data": {
        "positionId": 88004567,
        "symbol": "EURUSD",
        "name": "Euro vs US Dollar",
        "buySell": 1,
        "amount": 100.0,
        "openPrice": "1.08742",
        "closePrice": "0",
        "timeUnit": 60,
        "timeUnitType": "S",
        "openPositionTimestamp": 1710230461000,
        "settleTimestamp": 1710230521000,
        "result": 0,
        "resultAmount": "0",
        "grossProfit": "0",
        "productId": "1001"
      }
    }
  • Open (unliquidated) tickets

    POST /v1/tickets/open/query openfinance

    Lists tickets still running on the live book — the countdown row on the trade pad — with openPrice and settleTimestamp per positionId.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • pageNum
    • pageSize
    • positionId
    • symbol
    • buySell
    • amount
    • openPrice
    • closePrice
    • timeUnit
    • timeUnitType
    • openPositionTimestamp
    • settleTimestamp
    • endTime
    • result
    • grossProfit
    • isDeferred
    POST /v1/tickets/open/query HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "pageNum": 1,
      "pageSize": 20
    }
    {
      "respCode": "0000",
      "data": [
        {
          "positionId": 88004567,
          "symbol": "EURUSD",
          "name": "Euro vs US Dollar",
          "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
        }
      ]
    }
  • Settled ticket history

    POST /v1/tickets/settlements/query openfinance

    Pages settled tickets with openPrice versus closePrice, win/loss result and grossProfit after settleTimestamp.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body alongside pageNum and pageSize.

    • pageNum
    • pageSize
    • positionId
    • symbol
    • buySell
    • amount
    • openPrice
    • closePrice
    • result
    • resultAmount
    • grossProfit
    • timeUnit
    • openPositionTimestamp
    • closePositionTimestamp
    • settleTimestamp
    • bonusAmount
    POST /v1/tickets/settlements/query HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "pageNum": 1,
      "pageSize": 20
    }
    {
      "respCode": "0000",
      "data": [
        {
          "positionId": 88004510,
          "symbol": "EURUSD",
          "name": "Euro vs US Dollar",
          "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"
        }
      ]
    }
  • Create deposit order

    POST /v1/funding/orders/create openbanking

    Opens a funding order on UPI/Paytm (India) or a Pix/Cashfree rail. Returns orderNo, txnToken and the applied versus credited amount.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • amount
    • payType
    • payChannel
    • channelCode
    • upiId
    • paytmName
    • paytmNo
    • userEmail
    • userMobile
    • userName
    • orderNo
    • orderStatus
    • applyAmount
    • realAmount
    • currencyType
    • txnToken
    POST /v1/funding/orders/create HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "amount": "2000",
      "payType": "UPI",
      "payChannel": "PAYTM",
      "channelCode": "UPI",
      "upiId": "<upi-id>",
      "paytmName": "<account-holder>",
      "paytmNo": "<mobile-number>",
      "userEmail": "[email protected]",
      "userMobile": "<mobile-number>",
      "userName": "<account-holder>",
      "checkOutVersion": "local0"
    }
    {
      "respCode": "0000",
      "data": {
        "orderNo": "<funding-order-id>",
        "orderStatus": "01",
        "orderType": "01",
        "applyAmount": "2000",
        "realAmount": "2000",
        "payType": "UPI",
        "currencyType": "INR",
        "upiId": "<upi-id>",
        "paytmName": "<account-holder>",
        "paytmNo": "<mobile-number>",
        "txnToken": "<payment-transaction-token>",
        "applyTime": 1710231000000
      }
    }
  • Request withdrawal

    POST /v1/payouts/requests/create openbanking

    Submits a payout to a saved collection account (IFSC bank, Paytm or Pix). Response splits applyAmount, serviceFee and realAmount.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body. A separate fee preview can precede the payout request.

    • amount
    • collectionAccountId
    • collectionAccountType
    • holderName
    • mobile
    • paytmName
    • paytmNo
    • orderNo
    • orderStatus
    • applyAmount
    • realAmount
    • serviceFee
    • ifscCode
    • bankName
    • bankNum
    POST /v1/payouts/requests/create HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "amount": "1500",
      "collectionAccountId": "<destination-id>",
      "collectionAccountType": "BANK",
      "holderName": "<account-holder>",
      "mobile": "<mobile-number>",
      "paytmName": "<account-holder>",
      "paytmNo": "<mobile-number>"
    }
    {
      "respCode": "0000",
      "data": {
        "orderNo": "<funding-order-id>",
        "orderStatus": "10",
        "orderType": "10",
        "applyAmount": "1500",
        "realAmount": "1470",
        "serviceFee": "30",
        "currencyType": "INR",
        "ifscCode": "<ifsc-code>",
        "bankName": "<bank-name>",
        "bankNum": "<bank-account-number>",
        "collectionAccountType": "BANK",
        "applyTime": 1710231600000
      }
    }
  • Deposit and withdrawal ledger

    POST /v1/funding/ledger/query openbanking

    Pages the cash ledger filtered by orderType (deposit vs withdrawal), including UPI Paytm numbers and Pix keys when those rails were used.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • orderType
    • pageNum
    • pageSize
    • startTime
    • endTime
    • orderNo
    • orderStatus
    • applyAmount
    • realAmount
    • payType
    • currencyType
    • ifscCode
    • pixKey
    • pixType
    • bankName
    • paytmNo
    • applyTime
    POST /v1/funding/ledger/query HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>",
      "orderType": "01",
      "pageNum": 1,
      "pageSize": 20,
      "startTime": 1709222400000,
      "endTime": 1710230400000
    }
    {
      "respCode": "0000",
      "data": [
        {
          "orderNo": "<funding-order-id>",
          "orderStatus": "02",
          "orderType": "01",
          "applyAmount": "2000",
          "realAmount": "2000",
          "payType": "UPI",
          "currencyType": "INR",
          "ifscCode": "",
          "pixKey": "",
          "pixType": "",
          "bankName": "",
          "paytmNo": "<mobile-number>",
          "applyTime": 1710231000000
        }
      ]
    }
  • KYC snapshot

    POST /v1/identity/checks/snapshot osint

    Returns the India KYC record: Aadhaar head number, PAN number and image, plus userStatus used to gate deposits and withdrawals.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • fullName
    • mobilePhone
    • panCard
    • userStatus
    • enforcePanImg
    • payOrder
    • name
    • mobile
    • aadHeadNumber
    • panNum
    • panImg
    POST /v1/identity/checks/snapshot HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>"
    }
    {
      "respCode": "0000",
      "data": {
        "fullName": "<account-holder>",
        "mobilePhone": "<mobile-number>",
        "panCard": "<pan-number>",
        "userStatus": "1",
        "enforcePanImg": false,
        "payOrder": true,
        "prompt": false,
        "kycInfo": {
          "name": "<account-holder>",
          "mobile": "<mobile-number>",
          "aadHeadNumber": "<masked-aadhaar-number>",
          "userStatus": "1",
          "id": 4412
        },
        "kycPanInfo": {
          "panNum": "<pan-number>",
          "panImg": "<pan-image-reference>",
          "userId": "<user-id>"
        }
      }
    }
  • Payout collection account

    POST /v1/payouts/destinations/current openbanking

    Reads the saved payout destination: Pix key and CPF for Brazil, or IFSC bank fields for India, plus withDrawableValue and serviceFee.

    Auth: Session token obtained at sign-in, sent as token and userId in the JSON body.

    • collectionAccountId
    • collectionAccountType
    • pixKey
    • pixType
    • cpf
    • bankName
    • bankNumber
    • bankHolderName
    • ifscCode
    • mobilePhone
    • email
    • withDrawableValue
    • bonusAmount
    • serviceFee
    • isActivate
    POST /v1/payouts/destinations/current HTTP/1.1
    Content-Type: application/json
    
    {
      "userId": "<user-id>",
      "token": "<session-token>"
    }
    {
      "respCode": "0000",
      "data": {
        "collectionAccountId": "<destination-id>",
        "collectionAccountType": "PIX",
        "pixKey": "[email protected]",
        "pixType": "EMAIL",
        "cpf": "<cpf-number>",
        "bankName": "<bank-name>",
        "bankNumber": "<bank-account-number>",
        "bankHolderName": "<account-holder>",
        "ifscCode": "",
        "mobilePhone": "<mobile-number>",
        "email": "[email protected]",
        "withDrawableValue": "3200.00",
        "bonusAmount": "0",
        "serviceFee": "15.00",
        "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 and bonus from the wallet snapshot, the parallel simulation balance, then matches settled tickets on resultAmount and grossProfit so demo resets never mix with INR/BRL cash.

  • Timed-ticket blotter

    A desk overlay joins last-tick cp/pchg for a symbol with open unliquidated rows (openPrice, settleTimestamp, buySell) and pages history once result and closePrice land.

  • KYC gate before Pix or IFSC payout

    A withdrawals queue reads userStatus, aadHeadNumber and panNum, then only releases a withdraw row when the collection account's pixKey or ifscCode is active and withDrawableValue covers applyAmount plus serviceFee.

  • UPI and Pix funding tracker

    Treasury maps deposit orderNo, payType, upiId and txnToken against capital-list rows (realAmount, currencyType, pixKey) to see which India UPI and Brazil Pix rails actually credited.

Frequently asked questions

What quote and instrument fields does the GuruTrade7 data API illustrate?

Quote records include sb, showSymbol, last price cp, tick time ct, percentage change pchg, highPrice, lowPrice, openingTodayPrice and closedYesterdayPrice. The instrument catalog adds profit for payout percentage, min and max stake values, and settleType. Paths and sample values on this page are illustrative rather than production service addresses.

How do ticket outcomes and wallet fields support live-versus-practice reconciliation?

Ticket submission uses symbol, amount, buySell, profit, timeUnit and quotationTime. Active positions carry positionId, openPrice and settleTimestamp; settled history adds closePrice, result, resultAmount and grossProfit. Wallet records retain balance, bonus and simulation, with resetSuccess in the practice-wallet view. These fields support a blotter that follows positions from entry through expiry and reconciliation that keeps the simulation wallet separate from INR and BRL cash movements.

Which fields describe UPI, Pix and bank funding or payouts?

India funding examples include upiId, paytmName, paytmNo and txnToken. Brazil payout destinations include pixKey, pixType and cpf, while India bank destinations use ifscCode and bank details. Ledger and payout records distinguish orderNo, applyAmount, realAmount, serviceFee and currencyType.

What authentication and sensitive identity fields do the payout examples describe?

Email sign-in accepts email and password and returns access_token with userId and accountNumber. Authenticated examples pass the session credential as token alongside userId in the JSON body rather than an Authorization header. Identity records include userStatus, aadHeadNumber, panNum and panImg; saved payout destinations add isActivate, withDrawableValue and serviceFee for authorized eligibility checks. The paths and sample values are illustrative, not production service addresses or usable credentials. Tokens, personal identity details and account identifiers are placeholders.

Apps similar to Guru Trade7-Serving 7 Years

  • Olymptrade – Trading online — Olymptrade is a licensed online broker with Fixed Time, Forex and Stocks modes, Flex and InZone tickets, and a refillable demo account of 10,000 virtual units.
  • IQ Option – Trading Platform — IQ Option is a Limassol broker founded in 2013 that trades CFDs, forex, stocks and cryptocurrencies after shifting its focus from binary options.
  • Pocket Option — Pocket Option is a web and Android desk for quick and digital tickets on currencies, commodities and stocks, with a virtual-money demo account.
  • MetaTrader 4 Forex Trading — MetaTrader 4 is MetaQuotes' 2005 electronic trading platform, licensed to brokers so retail traders can stream quotes, chart and place forex and CFD orders on Windows, Android and iOS.
  • MetaTrader 5 — Forex, Stocks — MetaTrader 5 is MetaQuotes' 2010 successor to MT4, covering forex plus equities and exchange-traded commodities on desktop and mobile.
  • TradingView: Track All Markets — TradingView is a charting and social-markets platform whose Supercharts cover stocks, crypto, forex and futures and let users place trades through connected brokers.
  • Deriv — Deriv is an online broker operating since 1999 that offers CFDs and options on forex, stocks, commodities, crypto and 24/7 synthetic indices, plus Deriv MT5 and cTrader terminals.

Topics

  • gurutrade7 data api
  • guru trade7 quote fields
  • timed trading ticket data
  • live and demo wallet reconciliation
  • upi pix funding records
  • pan aadhaar verification status
  • trading payout destination fields

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

Get a quote