AIB Bullion API integration services (Gold & Silver MCX OpenData)

1. Live spot rate ingestion

A polling and websocket bridge that captures the AIB Bullion spot feed (SPOT GOLD, INT-GOLD, GOLD EFP, SPOT SILVER) and republishes it as JSON with millisecond timestamps. Used to drive in-store price boards, trading screen overlays and reconciliation jobs that compare AIB rates against IBJA and MCX benchmarks.

2. City-wise rate normaliser

A normalisation layer that maps the eight city blocks shown inside the app — Delhi, Mumbai, Jaipur, Hyderabad, Indore, Surat, Kochi, Ahmedabad — onto a single tabular schema with purity (24K/22K/18K), making/wastage charges and GST-inclusive variants. This is the format jewellery ERPs such as GehnaERP, Jwelly ERP and WinGold expect on their inbound rate hooks.

3. Market call & alert webhook

A push-style endpoint that forwards AIB analyst calls and major-movement alerts to Slack, Telegram, MS Teams or any internal trading desk. Each event carries call_id, instrument, side, entry, target, stop-loss and analyst tags so it can also feed P&L attribution and compliance archives.

4. MCX chart & historical OHLC export

Bulk export endpoint for candlestick and historical-fix data, with paged JSON and on-demand CSV/Excel snapshots. Powers technical-analysis notebooks, back-test rigs and compliance reports that need to re-create what an AIB user saw at a specific moment.

5. Wholesaler & jewellery design directory

Search and lookup endpoints over the verified wholesaler network and the jewellery design catalogue, returning vendor profile, contact channels, design SKUs and listed weight ranges. Helpful for B2B procurement portals and marketplace integrations.

6. Online booking & order sync

An order-tracking layer that mirrors the in-app gold/silver booking flow and exposes confirmation, status-change and settlement events to back-office systems, so a wholesaler can drop AIB-driven orders directly into their billing and inventory tooling.

Scenario A — Jewellery ERP price refresh

A multi-store jeweller in Gujarat needs the same spot price to drive its showroom display, its tag-printing service and its Tally/GST billing. We expose /v1/rates/spot?city=ahmedabad&purity=24K, push every tick into the ERP's webhook, and emit a daily IBJA-vs-AIB delta report so the finance team can spot drift before it shows up in margin reports.

Scenario B — Trading desk call distribution

A bullion broker wants to fan AIB analyst calls out to clients on Telegram, WhatsApp and a custom portal. Our adapter consumes the call stream, enriches each event with MCX last-traded-price and posts to the right channel under each user's consent record — an OpenFinance-style flow modelled after PSD2 strong-customer-authentication patterns.

Scenario C — Quant back-testing pipeline

A research team uses the historical OHLC export to back-test a momentum strategy on MCX gold mini contracts. We deliver a parquet snapshot of three years of one-minute candles plus a replay endpoint, so the simulator can recreate exactly what an AIB user saw at any prior timestamp.

Scenario D — Wholesaler procurement portal

A jewellery chain centralises bulk procurement by reading the AIB wholesaler directory and design catalogue into its own marketplace. We provide the listing/search APIs plus an opt-in lead webhook, so vendors only see enquiries from buyers they have agreed to engage with.

Scenario E — Compliance and analyst archive

An investment advisor regulated under SEBI's Research Analyst regime needs an immutable archive of every public call along with the live rate context at the moment of publication. We pair the calls API with a snapshot service that stores call_id, rate_at_publish, channel and acknowledgement records for audit replay.

Live spot rate fetch

GET /api/v1/aib/rates/spot?city=mumbai&purity=24K
Authorization: Bearer <ACCESS_TOKEN>
Accept: application/json

200 OK
{
  "city": "mumbai",
  "metal": "gold",
  "purity": "24K",
  "bid": 7421.50,
  "ask": 7425.10,
  "unit": "INR/g",
  "source": "AIB::SPOT_GOLD",
  "ts": "2026-04-29T08:14:31.224+05:30"
}

Market call webhook payload

POST https://your-app.example.com/hooks/aib/call
X-AIB-Signature: t=1714367671,v1=4f1b...c2
Content-Type: application/json

{
  "call_id": "AIB-2026-04-29-0173",
  "instrument": "MCXGOLDM-JUN26",
  "side": "BUY",
  "entry": 73210,
  "target": 73850,
  "stop_loss": 72940,
  "analyst": "desk-04",
  "issued_at": "2026-04-29T10:02:11+05:30"
}

Historical OHLC export

POST /api/v1/aib/history/ohlc
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "instrument": "MCXSILVER",
  "interval": "5m",
  "from": "2026-01-01T00:00:00+05:30",
  "to":   "2026-04-29T00:00:00+05:30",
  "format": "parquet"
}

202 Accepted
{ "job_id": "ohlc_8a91", "status_url": "/jobs/ohlc_8a91" }

Auth, retries and error handling

All endpoints sit behind rotating bearer tokens with HMAC-signed webhooks. Clients get an idempotency key on every write call, exponential-backoff guidance on 429/503, and a structured error envelope (code, message, retry_after, request_id) so failures are debuggable end-to-end. Source code ships in Python and Node.js with a typed SDK and contract tests.

Compliance & privacy

Bullion data in India sits at the intersection of several frameworks. We design every integration against:

• SEBI Cybersecurity and Cyber Resilience Framework (CSCRF), August 2024 — encryption at rest and in transit, third-party vendor controls and mandatory audits.
• SEBI Master Circular on Electronic Gold Receipts (June 2024) — vault-manager and grievance handling expectations when AIB booking flows touch EGR-backed gold.
• India Bullion & Jewellers Association self-regulatory body — IBJA reference rates and code-of-conduct alignment for analyst calls.
• Digital Personal Data Protection Act (DPDP), 2023 — consent, purpose limitation and data-principal rights for any user-identifying field.
• SEBI Research Analyst Regulations — immutable archive of published calls and disclosures.

Data flow / architecture

A typical AIB integration pipeline runs as a four-node flow:

• Client App / Capture — authorised mobile or server client mirrors the AIB endpoints and emits raw events.
• Ingestion / API gateway — normalises payloads, applies rate limits and signs outbound webhooks.
• Storage — hot store (Redis / Postgres) for live rates, cold store (S3 / Parquet) for OHLC and call archives.
• Analytics & API output — REST/JSON, websocket fan-out and BI connectors for downstream ERPs and dashboards.

Deliverables checklist

• API specification (OpenAPI / Swagger) for the AIB Bullion surface we mirror
• Protocol and auth flow report (token refresh, signature scheme, retry behaviour)
• Runnable source for spot rates, historical OHLC and call webhooks (Python / Node.js)
• Automated contract tests, sample payloads and Postman collection
• Compliance notes covering SEBI CSCRF, DPDP and IBJA reference-rate handling
• Optional hosted endpoints with pay-per-call billing and SLA

About us

We are an independent studio focused on fintech and OpenData API integration. Our engineers come from bullion trading desks, payments, mobile reverse engineering and cloud infrastructure, and we ship end-to-end financial APIs under security and compliance constraints.

• Bullion, payments, digital banking and cross-border clearing
• Enterprise API gateways and security reviews
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoint with no upfront cost

Contact

For quotes or to submit your target app and requirements, open our contact page:

Contact page

Engagement workflow

1. Scope confirmation: which AIB modules (rates, calls, OHLC, wholesalers, booking) you actually need.
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build, internal validation and contract tests (3–8 business days).
4. Documentation, samples and acceptance review (1–2 business days).
5. Typical first delivery: 5–15 business days; multi-source reconciliation may extend timelines.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?