Uni GoldX Data API: Endpoints and Fields
Uni: GoldX & UPI Credit Card is the Android app of Uni Cards, an Indian fintech that issues the GoldX credit card in partnership with Yes Bank and Bank of Baroda. It covers the whole card lifecycle: eligibility check and digital KYC, card activation, credit-limit selection, and a RuPay virtual companion card that can be added to Google Pay, PhonePe or Paytm for scan-and-pay UPI alongside the primary Visa or Mastercard. Rewards are the differentiator: spends earn Uni Coins at 100 coins to the rupee, and coins convert instantly into 24K digital gold held in a GoldX Vault backed by Augmont, with cash-out or a minted physical coin. The app also carries monthly statements, bill repayment, EMI and Pay Later conversion on individual purchases, card locks, PIN resets and per-channel transaction limits, plus a Uni Store for flight bookings and merchant vouchers. It is an India-only consumer credit-card app competing with HDFC, ICICI and Axis card apps, and holds a 4.5 rating from roughly 194,000 Play reviews.
GoldX Vault balances distinguish uniCoins and their rupee conversion rate, coinToRupeeRate, from gold holdings measured by goldGrams, goldValue and goldRatePerGram. Purchase records pair merchantName with uniCoinsEarned, while conversion results record coinsDebited, goldGramsCredited, uniCoinsAfter and goldGramsAfter; together these support rewards and gold-balance reconciliation. Statement payloads mirror the billing cycle — statementDate, totalAmountDue, minimumDue, dueDate and per-categoryCode spend rows — while the credit-line summary exposes creditLine, availableLimit and unbilledAmount for comparing available credit with billed and unbilled spending.
Transaction records add txnId, mcc, postedDate and txnStatus. EMI or Pay Later conversion results carry emiAmount, tenureMonths, interestRate, monthlyInstalment, processingFee and firstDueDate. Bill-payment payloads identify the debit-card or UPI instrument through instrumentType and vpa, with results recorded in paymentRef, paymentStatus, totalAmountDueAfter and creditLimitRestored. Card-control state lands as cardLocked, onlineLimit and perTxnLimit. Personal-finance aggregators can build spend-reconciliation views, accounting teams can compare coin earnings with gold conversions and balances, support teams can inspect card-control state, and lending analysts can compare instalment terms with repayment results. openData Studio turns these fields into callable open data.
Screenshots
API surface
Request/response examples are illustrative, reconstructed from the app's interface — not a live capture.
Verify mobile OTP session
POST
/v1/uni-card/session/otp-verifyopenbankingCompletes the SMS OTP step that opens the signed-in session and returns the customer id, token pair and the KYC and card states the home screen branches on.
Auth: None. Registered mobile number plus SMS OTP mint the accessToken and refreshToken; device binding and app-integrity headers are attached on later calls.
- mobileNumber
- otp
- deviceId
- appVersion
- customerId
- accessToken
- refreshToken
- tokenExpiry
- isNewUser
- kycStatus
- cardStatus
POST /v1/uni-card/session/otp-verify HTTP/1.1 Content-Type: application/json X-Device-Id: android-7f2c9a { "mobileNumber": "9876543210", "otp": "471029", "deviceId": "android-7f2c9a", "appVersion": "2.24.1" }{ "status": "SUCCESS", "data": { "customerId": "UNI-884213", "accessToken": "eyJhbGciOiJSUzI1NiJ9...", "refreshToken": "rt_5f81c2", "tokenExpiry": "2026-10-25T19:40:00+05:30", "isNewUser": false, "kycStatus": "VERIFIED", "cardStatus": "ACTIVE" } }KYC and onboarding status
GET
/v1/uni-card/onboarding/kyc-statusopenbankingReports where a customer sits in onboarding: Aadhaar and PAN checks, video KYC, address and document-camera proofs, and the approved credit limit that unlocks card generation.
Auth: Bearer accessToken from the OTP session; document and face steps run through the partnered identity SDK and post their references back.
- customerId
- aadhaarVerified
- panVerified
- vkycStatus
- addressStatus
- doccamUploaded
- eligibilityStatus
- approvedCreditLimit
- pendingStep
GET /v1/uni-card/onboarding/kyc-status HTTP/1.1 Authorization: Bearer <accessToken>{ "status": "SUCCESS", "data": { "customerId": "UNI-884213", "aadhaarVerified": true, "panVerified": true, "vkycStatus": "COMPLETED", "addressStatus": "VERIFIED", "doccamUploaded": true, "eligibilityStatus": "APPROVED", "approvedCreditLimit": 150000, "pendingStep": null } }Credit-line summary
GET
/v1/uni-card/credit-line/summaryopenfinanceHydrates the credit-line card on the home screen and the card summary: sanctioned line, available headroom, billed versus unbilled spend and the next due date.
Auth: Bearer accessToken from the OTP session.
- creditLine
- availableLimit
- usedLimit
- unbilledAmount
- billedAmount
- totalAmountDue
- minimumDue
- dueDate
- statementDate
- currency
GET /v1/uni-card/credit-line/summary HTTP/1.1 Authorization: Bearer <accessToken>{ "status": "SUCCESS", "data": { "creditLine": 150000, "availableLimit": 112480.5, "usedLimit": 37519.5, "unbilledAmount": 4210.0, "billedAmount": 33309.5, "totalAmountDue": 33309.5, "minimumDue": 1665.48, "dueDate": "2026-11-05", "statementDate": "2026-10-18", "currency": "INR" } }Reveal card details
POST
/v1/uni-card/card/detailsopenbankingServes the view-and-copy-card-details sheet, returning the masked number, expiry, card variant and the RuPay companion virtual card behind UPI.
Auth: Bearer accessToken plus a step-up OTP or device authentication; the reveal is short-lived and audited per card.
- cardId
- cardNumber
- cardHolderName
- expiryMonth
- expiryYear
- cvv
- cardType
- cardVariant
- network
- rupayVpa
POST /v1/uni-card/card/details HTTP/1.1 Authorization: Bearer <accessToken> Content-Type: application/json { "cardId": "card_goldx_01", "revealField": "FULL", "otp": "884120" }{ "status": "SUCCESS", "data": { "cardId": "card_goldx_01", "cardNumber": "4581 22XX XXXX 9043", "cardHolderName": "PRIYA SHARMA", "expiryMonth": "09", "expiryYear": "2029", "cvv": "***", "cardType": "MASTERCARD", "cardVariant": "GOLDX", "network": "DUAL", "rupayVpa": "priya.884213@uni" } }Card controls and limits
POST
/v1/uni-card/controls/limitsopenbankingReads and writes the card-control panel: lock state, channel toggles and the rupee limits for online, per-transaction and ATM use.
Auth: Bearer accessToken from the OTP session; sensitive switches re-prompt for MPIN or biometrics.
- cardId
- cardLocked
- onlineEnabled
- contactlessEnabled
- internationalEnabled
- onlineLimit
- perTxnLimit
- atmLimit
- updatedAt
POST /v1/uni-card/controls/limits HTTP/1.1 Authorization: Bearer <accessToken> Content-Type: application/json { "cardId": "card_goldx_01", "cardLocked": true, "onlineEnabled": true, "contactlessEnabled": false, "internationalEnabled": true, "onlineLimit": 50000, "perTxnLimit": 25000, "atmLimit": 10000 }{ "status": "SUCCESS", "data": { "cardId": "card_goldx_01", "cardLocked": true, "onlineEnabled": true, "contactlessEnabled": false, "internationalEnabled": true, "onlineLimit": 50000, "perTxnLimit": 25000, "atmLimit": 10000, "updatedAt": "2026-10-25T12:04:11+05:30" } }Transaction history
GET
/v1/uni-card/transactionsopenfinancePages the transaction feed behind the home list and the collated transaction view, with merchant, MCC, channel, status and the coins each purchase earned.
Auth: Bearer accessToken from the OTP session.
- page
- pageSize
- total
- txnId
- merchantName
- mcc
- amount
- currency
- postedDate
- txnStatus
- channel
- isEmi
- uniCoinsEarned
GET /v1/uni-card/transactions?from=2026-09-01&to=2026-10-25&page=1&pageSize=50 HTTP/1.1 Authorization: Bearer <accessToken>{ "status": "SUCCESS", "data": { "page": 1, "pageSize": 50, "total": 143, "transactions": [ { "txnId": "TXN8891243", "merchantName": "SWIGGY", "mcc": "5812", "amount": 842.0, "currency": "INR", "postedDate": "2026-10-22", "txnStatus": "POSTED", "channel": "ONLINE", "isEmi": false, "uniCoinsEarned": 842 } ] } }Monthly statement
GET
/v1/uni-card/statements/{statementId}openfinanceReturns a billing cycle as summary plus category rows: opening balance, payments, new purchases, amount due and the spend split the statement screen charts.
Auth: Bearer accessToken from the OTP session.
- statementId
- statementDate
- dueDate
- totalAmountDue
- minimumDue
- previousBalance
- paymentsReceived
- newPurchases
- categories
- categoryCode
- label
- amount
- lineItems
GET /v1/uni-card/statements/STMT-2026-10 HTTP/1.1 Authorization: Bearer <accessToken>{ "status": "SUCCESS", "data": { "statementId": "STMT-2026-10", "statementDate": "2026-10-18", "dueDate": "2026-11-05", "totalAmountDue": 33309.5, "minimumDue": 1665.48, "previousBalance": 28410.0, "paymentsReceived": 12000.0, "newPurchases": 16899.5, "categories": [ { "categoryCode": "DINING", "label": "Food & Dining", "amount": 4210.0 } ], "lineItems": 64 } }Repay card bill
POST
/v1/uni-card/repaymentopenbankingPlaces a bill payment from a debit card or UPI VPA, supports minimum-due, total-due and custom amounts, and returns the reference plus the restored limit.
Auth: Bearer accessToken plus the payment instrument session; card and UPI instruments are tokenised before the debit.
- amount
- instrumentType
- vpa
- repaymentType
- paymentRef
- paymentStatus
- totalAmountDueAfter
- creditLimitRestored
- lateFeeWaived
POST /v1/uni-card/repayment HTTP/1.1 Authorization: Bearer <accessToken> Content-Type: application/json { "amount": 1665.48, "instrumentType": "UPI", "vpa": "priya@okhdfcbank", "repaymentType": "MINIMUM_DUE" }{ "status": "SUCCESS", "data": { "paymentRef": "PAY-7719032", "amount": 1665.48, "instrumentType": "UPI", "vpa": "priya@okhdfcbank", "paymentStatus": "PROCESSING", "totalAmountDueAfter": 31644.02, "creditLimitRestored": 112480.5, "lateFeeWaived": true } }Convert purchase to EMI or Pay Later
POST
/v1/uni-card/transactions/{txnId}/convertopenfinanceConverts a posted purchase into a tenure-based EMI or a Pay Later plan, returning the monthly instalment, rate, processing fee and the loan id that the repayment schedule hangs off.
Auth: Bearer accessToken from the OTP session.
- txnId
- conversionType
- convertedAmount
- emiAmount
- tenureMonths
- interestRate
- monthlyInstalment
- processingFee
- firstDueDate
- loanId
POST /v1/uni-card/transactions/TXN8891243/convert HTTP/1.1 Authorization: Bearer <accessToken> Content-Type: application/json { "conversionType": "EMI", "tenureMonths": 6, "planId": "PLAN_6M_LOW" }{ "status": "SUCCESS", "data": { "txnId": "TXN8891243", "conversionType": "EMI", "convertedAmount": 842.0, "emiAmount": 147.9, "tenureMonths": 6, "interestRate": 15.99, "monthlyInstalment": 147.9, "processingFee": 99.0, "firstDueDate": "2026-11-05", "loanId": "EMI-449021" } }Uni Coins and GoldX Vault
GET
/v1/uni-card/rewards/vaultopenfinanceReturns the rewards ledger and the GoldX Vault: coin balance at the 100-coins-to-the-rupee rate, gold grams held with the custodian, and their live rupee value.
Auth: Bearer accessToken from the OTP session.
- uniCoins
- coinToRupeeRate
- goldGrams
- goldValue
- goldPurity
- custodian
- lifetimeCoinsEarned
- pendingCoins
- goldRatePerGram
GET /v1/uni-card/rewards/vault HTTP/1.1 Authorization: Bearer <accessToken>{ "status": "SUCCESS", "data": { "uniCoins": 128400, "coinToRupeeRate": 0.01, "goldGrams": 0.6421, "goldValue": 7480.3, "goldPurity": "24K", "custodian": "AUGMONT", "lifetimeCoinsEarned": 902140, "pendingCoins": 1840, "goldRatePerGram": 11649.0 } }Convert coins to gold or cashback
POST
/v1/uni-card/rewards/convertopenfinanceBurns Uni Coins into 24K digital gold in the vault or a cashback credit, recording the grams credited at the day's gold rate and the post-conversion balances.
Auth: Bearer accessToken from the OTP session.
- coins
- conversionType
- redeemMode
- conversionId
- coinsDebited
- goldGramsCredited
- goldRatePerGram
- uniCoinsAfter
- goldGramsAfter
- settlementStatus
POST /v1/uni-card/rewards/convert HTTP/1.1 Authorization: Bearer <accessToken> Content-Type: application/json { "coins": 50000, "conversionType": "GOLD", "redeemMode": "VAULT" }{ "status": "SUCCESS", "data": { "conversionId": "CVT-33907", "coinsDebited": 50000, "conversionType": "GOLD", "goldGramsCredited": 0.0429, "goldRatePerGram": 11649.0, "uniCoinsAfter": 78400, "goldGramsAfter": 0.685, "settlementStatus": "SUCCESS" } }UPI scan and pay
POST
/v1/uni-card/upi/scan-payopenbankingPays a merchant VPA over UPI from the RuPay credit-card companion, returning the UPI reference, the coins earned and the credit limit left after the debit.
Auth: Bearer accessToken plus the UPI PIN entered in the device keystore; the RuPay companion card funds the debit.
- vpa
- amount
- currency
- note
- instrument
- upiTxnId
- txnStatus
- uniCoinsEarned
- availableLimitAfter
- merchantName
POST /v1/uni-card/upi/scan-pay HTTP/1.1 Authorization: Bearer <accessToken> Content-Type: application/json { "vpa": "merchant@okaxis", "amount": 350.0, "currency": "INR", "note": "Groceries", "instrument": "RUPAY_CC" }{ "status": "SUCCESS", "data": { "upiTxnId": "UPI4471920", "vpa": "merchant@okaxis", "amount": 350.0, "instrument": "RUPAY_CC", "txnStatus": "SUCCESS", "uniCoinsEarned": 350, "availableLimitAfter": 112130.5, "merchantName": "SHARMA STORES" } }
Data categories
- card and credit-line state
- card controls and limits
- transaction history
- monthly statements and spend categories
- bill repayment records
- EMI and Pay Later conversions
- Uni Coins rewards
- 24K digital gold vault
- UPI VPA payments
- KYC and onboarding status
Where teams use this data
Spend reconciliation for card portfolios
A personal-finance aggregator pages txnId, merchantName, mcc, postedDate and txnStatus from the transaction feed, joins them to the statement's categoryCode rows, and reconciles billed versus unbilled spend using totalAmountDue, minimumDue and dueDate from the credit-line summary.
Rewards-to-gold ledger
An accounting job tracks uniCoinsEarned per purchase against the vault's uniCoins and goldGrams, prices conversions at goldRatePerGram, and flags any conversion where goldGramsCredited does not match coinsDebited at the 100-coins-to-the-rupee rate.
Card-ops control plane
A support console reads cardLocked, onlineEnabled, internationalEnabled, perTxnLimit and atmLimit so an agent can confirm channel state before reissuing or unlocking a card, and reads cardType, cardVariant and network to identify the RuPay companion used for UPI.
EMI and repayment analysis
A lending analytics pipeline collects emiAmount, tenureMonths, interestRate, processingFee and monthlyInstalment from conversion responses, then matches paymentRef and paymentStatus rows from repayments to compute how much of each bill was actually settled.
Frequently asked questions
What data does the Uni GoldX app expose?
A credit-line summary (creditLine, availableLimit, usedLimit, unbilledAmount, totalAmountDue, minimumDue, dueDate), a paged transaction feed (txnId, merchantName, mcc, postedDate, txnStatus, uniCoinsEarned), monthly statements with spend categoryCode rows, EMI conversion results (emiAmount, tenureMonths, interestRate, monthlyInstalment) and the rewards vault (uniCoins, goldGrams, goldValue, goldRatePerGram).
How are card sessions and sensitive card or UPI actions authenticated?
A mobile number plus SMS OTP returns accessToken and refreshToken for a device-bound session; later calls use the access token as a Bearer credential. Revealing card details adds a step-up OTP or device authentication, and sensitive card-control changes can require MPIN or biometrics. Merchant UPI payments require a UPI PIN in addition to the Bearer session.
How are GoldX rewards represented in the API?
Spends earn Uni Coins at 100 coins to the rupee. The vault endpoint returns uniCoins, coinToRupeeRate, goldGrams, goldValue and goldRatePerGram, and the conversion endpoint returns coinsDebited, goldGramsCredited and the post-conversion balances so a gold ledger can be reconstructed.
Which fields support statement, repayment and EMI reconciliation?
Statements contain statementId, statementDate, totalAmountDue, minimumDue, previousBalance, paymentsReceived and category rows. Bill-payment submissions return paymentRef, paymentStatus, totalAmountDueAfter and creditLimitRestored. Transaction-conversion submissions return loanId, emiAmount, tenureMonths, interestRate, monthlyInstalment, processingFee and firstDueDate, allowing repayment results to be compared with bill amounts and instalment terms.
Apps similar to Uni: GoldX & UPI Credit Card
- OneCard — OneCard is an Indian metal credit card from FPL Technologies, issued with bank partners such as BOBCARD, Federal Bank and SBM Bank; the OneCard app is used to set spend limits, toggle domestic, international, online, offline and contactless use, and convert purchases to EMI.
- Slice — Slice issues a UPI credit card that can be spent wherever UPI is accepted online or offline, alongside weekly merchant cashback sparks and a zero-balance savings account.
- CRED — CRED is a members-only Indian app for paying and managing credit-card bills with due-date reminders and spending insights, and for scanning UPI QR codes or tapping to pay on credit.
- iMobile — iMobile is ICICI Bank's official mobile banking app; customers use it to apply for credit cards, manage debit, credit and forex cards, and get an instant RuPay credit card for UPI.
- Axis Mobile — Axis Mobile (open by Axis Bank) is Axis Bank's official mobile banking app, advertised for 250+ services including UPI scan-and-pay and credit-card access.
- PayZapp — PayZapp is HDFC Bank's app for UPI, bill payments and recharges, and it also issues Pixel digital credit cards that are applied for, managed, rewarded and repaid inside the same app.
- RBL MyCard — RBL MyCard is RBL Bank's official Android app for its credit cards, used to check statements, pay the card bill and review recent activity.
- SBI Card — SBI Card is the State Bank of India group's credit-card issuer; its site lists a mobile app among payment modes and lets cardholders pay dues, view statements, manage PIN, book Flexipay EMI and report a lost card.
Topics
- Uni Cards API
- GoldX credit card API
- Uni Coins digital gold
- credit-line availableLimit
- card statement totalAmountDue
- EMI conversion emiAmount
- UPI scan and pay VPA
- card controls perTxnLimit
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