BricTrade API integration & trading data export services

1. Login & session APIs

Mirrors the BricTrade mobile authentication flow. Handles email/phone login, one-time password verification, device binding and silent token refresh. A single call returns a long-lived session handle that downstream services reuse for statement and order queries without re-prompting the end user.

2. Trade history API

Pulls the full order and execution log: instrument symbol, direction (call/put for digital options, buy/sell for spot), stake (from the ₹20 minimum), payout, expiry timestamp and result. Supports date-range, symbol, and account-type (demo vs live) filters with cursor pagination for accounts containing tens of thousands of trades.

3. Balance & wallet sync

Real-time balance snapshot for the live rupee wallet, the reloadable demo balance, and any locked margin. A webhook channel emits a balance-changed event whenever a deposit, withdrawal or settlement clears, which downstream ERP or reconciliation services can subscribe to for near real-time bookkeeping.

4. Deposit & withdrawal ledger

Exports BricTrade deposit and withdrawal records together with the payment method (UPI, card, net banking, wallet). Each row carries a method-level reference ID so finance teams can reconcile inbound settlements against PSP statements without manual lookup.

5. Market data pass-through

Thin wrapper that re-exposes the instrument prices the BricTrade app shows — tick bid/ask, candle history and payout percentage for digital options — so algo strategies, back-testers and alerting tools can observe the exact data an end user sees in the mobile app.

6. Support & notification feed

Optional channel that surfaces the in-app chat and push notification stream: margin alerts, KYC requests and 24/7 support ticket events. Useful for CRM automation or compliance teams that need a timeline of all customer interactions.

Scenario A — Unified retail trading dashboard

Business context: a personal finance startup wants to show its users one consolidated view of positions held on BricTrade alongside spot crypto on CoinDCX and equities on a discount broker.

Data & APIs: the /v1/positions snapshot plus a 15-second webhook from /v1/balance/events; payloads are normalized into an OpenFinance-style Investment resource (instrument, quantity, costBasis, currentValue).

OpenData mapping: mirrors the "Investments" entity in consumer-finance open banking schemas so downstream screens do not need BricTrade-specific logic.

Scenario B — Tax filing & CA workbook export

Business context: Indian retail users need yearly trade books for capital gains filing. The app description highlights a ₹20 minimum ticket, which means accounts commonly accumulate thousands of small executions.

Data & APIs: /v1/trades?from=…&to=…&format=xlsx returns a pre-formatted workbook with ISIN-like instrument codes, holding period, and realized P&L.

OpenData mapping: conforms to the "Transactions" slice of OpenFinance specifications, ready for ingestion by Cleartax-style filing tools.

Scenario C — Risk control for prop-desk style teams

Business context: a small trading desk allocates demo balances to trainees and wants to observe behavior before any capital is deployed.

Data & APIs: subscription to /v1/orders/stream and the demo-account balance channel; the backend tags each event with account_type=demo.

OpenData mapping: an extension of OpenBanking event streams, adapted for retail brokerage surfaces.

Scenario D — PSP reconciliation for cross-border rupee flows

Business context: the operator that runs BricTrade receives payments through multiple processors (UPI, net banking, cards); treasury teams must match inbound funds with internal ledger entries.

Data & APIs: /v1/cashflow exports each deposit/withdrawal with PSP reference IDs, so the ERP can match them against gateway statements.

OpenData mapping: equivalent to the "Payments" OpenFinance domain, applied to broker cash-in/out flows.

Scenario E — Compliance audit trail & RBI alert-list diligence

Business context: BricTrade appears on the RBI Alert List of unlicensed forex trading platforms. Enterprises that serve Indian users need a documented paper trail for any downstream integration with such platforms.

Data & APIs: every API call is logged with consent record, requesting IP, data scope, and retention timer; exportable for internal compliance reviews.

OpenData mapping: follows the SEBI 2025 API-trading circular's guidance on five-year audit trails, adapted to third-party integrators.

Login & token exchange

// Exchange BricTrade credentials for a session token
POST /api/v1/brictrade/auth/login
Content-Type: application/json

{
  "email": "user@example.com",
  "otp": "123456",
  "device_fingerprint": "ios-2.5.6-abc"
}

// 200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "r_9f8a...",
  "expires_in": 3600,
  "account_type": "live"
}

Trade history export

// Paginated trade export (JSON or xlsx)
GET /api/v1/brictrade/trades
  ?from=2026-01-01&to=2026-03-31
  &asset_class=crypto,forex,stock
  &account=live
  &cursor=eyJwIjoyfQ
Authorization: Bearer <ACCESS_TOKEN>

// 200 OK
{
  "trades": [
    {
      "id": "t_8814",
      "symbol": "BTC/USDT",
      "direction": "buy",
      "stake_inr": 50.00,
      "payout_pct": 0.87,
      "opened_at": "2026-02-14T09:12:03Z",
      "closed_at": "2026-02-14T09:13:03Z",
      "pnl_inr": -50.00,
      "account_type": "live"
    }
  ],
  "next_cursor": "eyJwIjozfQ"
}

Balance-change webhook

// Subscriber receives a POST whenever
// a deposit, withdrawal or trade settles.
POST https://client.example.com/hooks/brictrade
X-Signature: sha256=abc...
Content-Type: application/json

{
  "event": "balance.updated",
  "account_id": "a_199","account_type": "live",
  "currency": "INR",
  "balance_before": 2130.00,
  "balance_after":  2080.00,
  "delta": -50.00,
  "reason": "trade_settled",
  "reference": "t_8814",
  "ts": "2026-02-14T09:13:04Z"
}

// Error response contract:
// 4xx -> auto retry with exponential backoff
// 5xx -> dead-letter after 6 attempts

Compliance & privacy

Any integration with a retail trading app in India must respect the SEBI 2025 API-trading framework (static IP binding for programmatic clients, mandatory two-factor authentication, and an audit trail retained for at least five years), the RBI guidance on unlicensed forex platforms — BricTrade is presently on the RBI Alert List — and the Digital Personal Data Protection Act, 2023 for any personal or financial data that crosses Indian borders.

We also design every pipeline to be GDPR-aware when integrators serve EU residents: explicit consent capture, purpose limitation, and on-demand data deletion. For broker-side agreements we align with ISO 27001 control families; for messaging and storage we default to TLS 1.2+ in flight and AES-256 at rest.

Data flow & architecture

A standard BricTrade integration follows four stages: Client App → Auth / Ingestion Gateway → Normalization & Storage → Client-facing API or Analytics sink.

• Client App: the mobile or web surface where the user authorizes access.
• Ingestion Gateway: a protocol-analysis layer that speaks BricTrade's native calls and rate-limits them.
• Normalization & Storage: maps raw payloads into OpenFinance-style schemas, deduplicates, and persists to Postgres + object storage for exports.
• Output: REST/GraphQL for dashboards, Kafka or webhooks for event consumers, Excel/PDF for CA and compliance teams.

Deliverables checklist

• API specification (OpenAPI 3.1 / Swagger)
• Protocol and auth flow report (OTP, token refresh, device binding)
• Runnable source for login, trade and balance APIs (Python / Node.js / Go)
• Automated test suite with fixtures for demo vs live accounts
• Compliance guidance aligned to SEBI 2025 and DPDP Act 2023
• Excel and PDF statement templates for CA filing

Engagement models

• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost.

About us

We are an independent technical service studio specializing in App interface integration and authorized API delivery. Our engineers have years of hands-on experience in mobile fintech, payments, and protocol analysis, and we ship production-ready connectors for consumer finance platforms across South and Southeast Asia, the Middle East, and Latin America.

• Financial and banking Apps — transactions, statements, integration pipelines
• E-commerce, delivery and retail Apps — orders, payments, inventory sync
• Hotel, travel and mobility Apps — bookings, itineraries, settlement
• Social, OTT media and dating Apps — authentication, messaging, profile
• Two engagement models: source-code delivery from $300, or pay-per-call hosted APIs

Contact

To request a quote or submit the target app and requirements for BricTrade-Profit for everyone, use our contact page. We respond within one business day and can sign an NDA before any data sample is exchanged.

Go to contact page

Engagement workflow

1. Scope confirmation — name the target integrations (login, trade history, balance, deposits).
2. Protocol analysis and API design — typically 2–5 business days.
3. Build and internal validation against demo and live accounts — 3–8 business days.
4. Documentation, samples and automated tests — 1–2 business days.
5. First delivery: usually 5–15 business days; third-party sandbox approvals may extend the timeline.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Can you also integrate CoinDCX, Zerodha, Groww or Binance alongside BricTrade?