IPO Bulk Apply - NEPSE & IPO API integration services

Source-code drop

• OpenAPI 3.1 spec covering IPO, allotment, NEPSE and portfolio routes
• Python (FastAPI) and Node.js (Fastify) reference servers
• Background workers for CDSC polling and NEPSE WebSocket fan-out
• Postman collection plus pytest / Jest test suite with fixtures
• Runbook covering MeroShare login flow, captcha handling and error retries

Operational artefacts

• Encrypted credential vault design (AES-256-GCM, per-tenant KMS keys)
• Audit log schema for every IPO submission and allotment fetch
• Rate-limit and back-off table per upstream system (CDSC, NEPSE, broker TMS)
• Compliance memo covering SEBON, CDSC and NEPSE redistribution boundaries
• SLA and observability checklist (Prometheus exporters, structured logs)

Hosted option (pay-per-call)

• Endpoints reachable over HTTPS with API-key + HMAC signature auth
• Per-call billing for IPO submission, allotment lookup and floorsheet pulls
• Webhook delivery for allotment results and price alerts
• Sandbox tenant for integration testing before production cutover

1. Multi-account IPO submission desk

A family office or share-management consultancy holds dozens of MeroShare DEMAT accounts on behalf of clients. We build a tenant-aware backend that accepts a list of {boid, bank_id, units}, signs each into MeroShare with stored credentials, posts the application and reconciles against the bank's ASBA debit. This mirrors the bulk-apply behaviour of CLI tools like nepseutils and nepse-ipo, but with audit logging suitable for a regulated client.

2. Allotment notification micro-service

The CDSC allotment portal publishes results per company. Our integration polls iporesult.cdsc.com.np on the issuer's expected schedule, normalises the response into allotted / not_allotted / pending, fans the rows back into MeroShare BOIDs and pushes them to your channel of choice — webhook, SMS gateway, Telegram bot or email — within seconds of publication.

3. Wealth dashboard with portfolio sync

For a wealth-tech product targeting Nepali professionals abroad, we expose a POST /portfolio/import route that accepts a MeroShare CSV or a TMS Excel sheet, normalises symbols against NEPSE master data and computes returns against the live index. Consent is recorded once and refreshed via OAuth-style token rotation; this is the same OpenFinance pattern used elsewhere for bank-statement aggregation.

4. Broker compliance & surveillance feed

NEPSE's TMS is integrated with the connectIPS payment gateway and exposes per-broker fill data. We turn that into a streaming feed of trades, settlement events and collateral movements that a broker's compliance team can replay into surveillance tooling — useful for spotting wash trades, layering and unusual cross-symbol activity around IPO listings.

5. Cross-border investor data room

Diaspora investors in the UAE, Australia and the US increasingly hold Nepalese shares. We provide a single OAuth-protected API that consolidates IPO history, holdings, dividends and bonus shares into one canonical JSON, ready for Plaid-style aggregation into expat-focused budgeting and tax tools.

Auth — bind a MeroShare DEMAT account

POST /api/v1/meroshare/bind
Content-Type: application/json
Authorization: Bearer <TENANT_TOKEN>

{
  "dpId": "13700",
  "username": "1234567890",
  "password": "<ENC:AES-256-GCM>",
  "clientCode": "ABCD-001"
}

200 OK
{
  "accountId": "ms_8f1a...",
  "boid": "1301370000123456",
  "name": "Ishwor P.",
  "tokenExpiresAt": "2026-05-08T18:30:00Z"
}

Bulk IPO submission

POST /api/v1/ipo/bulk-apply
Authorization: Bearer <TENANT_TOKEN>

{
  "issueId": "CIT-2026-MAY",
  "applications": [
    {"accountId":"ms_8f1a...","units":10,"bankId":"NIBL"},
    {"accountId":"ms_2b44...","units":10,"bankId":"NMB"}
  ]
}

207 Multi-Status
{
  "results": [
    {"accountId":"ms_8f1a...","status":"submitted","crn":"CRN1234567"},
    {"accountId":"ms_2b44...","status":"failed",
     "error":{"code":"ASBA_INSUFFICIENT","message":"Bank balance below issue amount"}}
  ]
}

NEPSE floorsheet — webhook subscription

POST /api/v1/nepse/webhooks
Authorization: Bearer <TENANT_TOKEN>

{
  "event": "floorsheet.row",
  "filter": {"symbol":"NABIL","minQty":500},
  "callbackUrl": "https://example.com/hooks/nepse",
  "secret": "whsec_..."
}

201 Created
{ "subscriptionId": "sub_91ab...", "active": true }

# Each delivered event:
{
  "ts": "2026-05-08T10:42:11+05:45",
  "symbol": "NABIL",
  "buyer": "BR58", "seller": "BR42",
  "qty": 800, "price": 715.00,
  "txId": "TXN-2026050810-000128"
}

Regulatory landscape

Nepal's capital market is regulated by the Securities Board of Nepal (SEBON), with depository services delivered by CDS and Clearing Ltd. (CDSC) through MeroShare and trading routed via NEPSE's NOTS/TMS stack. SEBON has continued to tighten rules on investment companies through 2024 and 2025, and any commercial redistribution of NEPSE market data requires a license from NEPSE or an authorized vendor — we model this constraint directly into the API's terms of use.

Data minimisation & consent

We collect only what each scenario requires: IPO submission needs DEMAT credentials, but a portfolio dashboard does not need transaction PINs. Consent records are timestamped, scoped per data domain and revocable through a single API call. PII like BOID and bank account numbers is hashed at rest where the use case allows; raw values are returned only to authenticated tenants over TLS 1.3.

Operational guardrails

Rate limits respect the upstream systems: MeroShare and CDSC are polled with jitter to avoid pressuring their portals during result publication. Failed submissions surface specific error codes (ASBA_INSUFFICIENT, BOID_INACTIVE, ISSUE_CLOSED) instead of generic 500s, so retry logic on your side stays predictable. All operations are logged for at least 12 months for regulator response and incident review.

MeroShare

The official CDSC depository app: holds the canonical BOID record, IPO/FPO/right-share applications and the EDIS share-transfer flow that every other Nepali stock app ultimately relies on.

Share Hub - NEPSE Information

A widely used NEPSE companion with its own bulk IPO result checker; teams often want a unified API that reconciles Share Hub watchlists with IPO Bulk Apply submissions.

ShareSansar

Nepal's leading financial-news portal; integration buyers usually pair NEPSE price feeds with ShareSansar's IPO calendar and dividend disclosures for a single editorial-grade dataset.

MeroLagani

A long-running portal for fundamental investors with company financials, ratios and dividend history; many ETL pipelines fan MeroLagani fundamentals into the same database that stores IPO Bulk Apply submissions.

NEPSE Alpha

Known for technical-analysis charts and SastoShare research tools; common integration request is to overlay NEPSE Alpha indicators on top of the holdings ingested through IPO Bulk Apply's portfolio import.

Nepalytix

Focuses on AI-driven stock insights and live NEPSE analytics; cross-app integrations frequently combine Nepalytix risk scores with allotment results pulled through our APIs.

Mr NEPSE - Bulk IPO Checker

A Nepali bulk IPO result checker on Android with TMS and MeroShare integration; teams running both products often want a single allotment ledger across the two apps.

NepseFolio

A web-first NEPSE portfolio tracker; integrators can map NepseFolio holdings onto the same canonical schema we use for IPO Bulk Apply portfolio imports.

Sastoshare

Part of the NEPSE Alpha family, popular for advanced trading and analysis tooling; relevant when downstream consumers want indicator series alongside IPO submission outcomes.

Share Alpha: NEPSE IPO & AI

An iOS NEPSE/IPO companion with AI summarisation; complements IPO Bulk Apply for users who want narrative summaries of allotment and market events.

About OpenFinance Lab

We are an independent technical studio focused on App protocol analysis, OpenData and OpenFinance integration. The team has spent years inside payments, depositories and trading systems across South Asia, the Gulf and Southeast Asia, which is why we feel at home with stacks like CDSC's MeroShare and NEPSE's NOTS/TMS. We deliver runnable source code, OpenAPI specs and an operational runbook — not just a deck.

• Capital markets, depositories, payments and digital banking
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance review
• Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted endpoints and pay only per call, no upfront cost; ideal for usage-based teams

Contact

Bring us your target app and the exact data you need. We reply with scope, price, and a delivery plan within one business day.

Open contact page

Engagement workflow

1. Scope confirmation — which IPO Bulk Apply / NEPSE / MeroShare flows you need.
2. Protocol analysis & API design (2–5 business days, scenario-dependent).
3. Build and internal validation against sandbox accounts (3–8 business days).
4. Documentation, sample apps and test cases (1–2 business days).
5. First delivery in 5–15 business days; CDSC or broker approvals can extend timelines.

FAQ

What do you need from me to start an IPO Bulk Apply integration?

How long does delivery of a NEPSE / MeroShare integration take?

How do you handle compliance with SEBON, CDSC and NEPSE rules?

Can the integration drive multiple DEMAT accounts at once?