How to Buy NEPSE API Access — Process, Procedure, and Guidelines

If you're building any kind of product on top of Nepal Stock Exchange data — a broker dashboard, an algorithmic trading engine, a research platform, an internal back-office tool, a mobile app — the single most consequential decision you'll make in year one is whether to license data directly from NEPSE or stitch together unofficial feeds. The official path takes weeks and costs money. The unofficial path takes hours and costs nothing — until the day your scraper breaks or NEPSE quietly issues a cease-and-desist. This article walks through the official procurement process so you can make that decision with eyes open.

We're going to cover: who NEPSE will license data to, what the application process looks like, which documents to prepare, the typical fee structure, the technical hand-off, the realistic timeline, and the common gotchas. Every concrete number — fees, deposit amounts, contact phone, validity period — should be confirmed against the official PDF below before you sign anything, because NEPSE refreshes the schedule periodically.

1. What you're actually licensing

NEPSE's API offering covers different slices of the market data the exchange itself produces. Depending on the package you select, that can include live ticker quotes, the full daily floorsheet (every executed contract — buyer, seller, symbol, quantity, rate, time), market depth (order book aggregates), index intraday ticks, sector indices, listed-security metadata, corporate-action filings (IPOs, FPOs, dividends, rights, bonus issues), and end-of-day OHLCV summaries.

Not all of these are sold as a single bundle. NEPSE typically tiers access by what the data is used for — internal use vs. redistribution, real-time vs. delayed, full floorsheet vs. summary only. Read the schedule carefully and match it to your product: a research platform that publishes delayed quotes needs a different licence than a broker's order-management system showing live depth to authenticated users.

2. Who can apply

NEPSE will entertain API-access applications from registered Nepali institutions across several categories — broadly:

• SEBON-licensed stockbrokers, merchant bankers, and depositary participants.
• Banks and financial institutions licensed by NRB that need market data for their treasury / wealth-management operations.
• Registered companies building software or analytics products for the Nepali capital markets (fintechs, data vendors, advisory platforms).
• Universities and research institutions with a documented academic-research use case.
• Media organisations publishing market-data segments.

Individuals usually cannot get a direct API licence. If you're an indie developer or analyst, you'll need to either incorporate a private limited company, partner with an already-licensed institution, or — what most people end up doing — work against publicly-available endpoints with the understanding that those are best-effort, not contractual.

3. The application process, end-to-end

The process roughly looks like this:

1. Send a formal request to NEPSE's IT / Vendor Management division identifying your organisation, the data tier you want, and the intended use case.
2. NEPSE returns the current data-licensing schedule (the PDF linked above) along with the prescribed application form.
3. You fill the form, attach the supporting documents (see next section), and submit physically at NEPSE's Singha Durbar Plaza office along with the application fee.
4. NEPSE reviews — the IT team checks technical fit, the legal/compliance team checks regulatory standing.
5. On approval, NEPSE issues a quotation for the data-access fee and (typically) a refundable security deposit. You pay both.
6. Sign the formal Data Access Agreement — this is the contract governing scope, duration, redistribution rules, and termination.
7. NEPSE provisions API credentials, hands over the technical documentation, and (usually) does a one-time onboarding call with your engineering team.
8. Annual renewal — most agreements are 12-month with an explicit renewal clause; missing the renewal window will get your keys deactivated.

4. Documents to prepare

Have these ready before you walk into the NEPSE office — going back and forth costs days each round:

• Company registration certificate (PAN/VAT certificate too).
• Memorandum and Articles of Association.
• Latest audited financial statements (typically the last 2 years).
• Tax clearance certificate.
• SEBON / NRB licence (if you hold one — required for broker / BFI / merchant-banker categories).
• Board / management resolution authorising the application and naming the signatory.
• Citizenship of the authorised signatory.
• A written technical brief: the data tier requested, expected request volume, intended use, redistribution scope, and data-retention policy.
• Application fee (NEPSE typically asks for this upfront with the form, separate from the data-access fee).

5. Typical fee structure

The fee schedule has historically had two layers: a one-time / non-refundable connection fee, plus a recurring annual subscription. On top of that NEPSE generally requires a refundable security deposit held for the duration of the contract. The exact numbers are in the PDF and have been revised more than once — what's stable is the structure, not the values:

• Application / processing fee — flat, non-refundable, paid with the form.
• Annual data-access fee — tier-dependent, recurring, paid before key provisioning and again at each renewal.
• Refundable security deposit — held for the duration of the contract, returned on graceful termination minus any deductions.
• Per-symbol or per-call fees — uncommon but appear in some redistribution tiers.

For a small Nepali fintech using the data internally, you should budget into the high six-figure NPR range for first-year all-in cost — between the application fee, security deposit, annual fee, and the time-and-materials cost of legal review. For redistribution tiers (publishing the data onward), expect the annual fee to be materially higher.

6. Technical hand-off

Once contracts and payments clear, NEPSE provisions an API account and shares technical documentation. Practical expectations:

• Authentication is typically via assigned credentials (client ID / secret or API key) bound to your registered IP range. Whitelist your egress IPs in advance.
• Endpoints are HTTP/JSON — predictable, but the schemas are tuned for NEPSE's internal needs rather than for downstream developer ergonomics. Plan for a thin adapter layer in your codebase.
• Rate limits and concurrent-request caps are documented in the agreement. Exceeding them can trigger automated throttling first, then a contractual notice.
• WebSocket / streaming endpoints exist for some real-time tiers; polling endpoints exist for everything else.
• Test / staging environment may or may not be offered depending on the tier — confirm at contract-signing time.
• Versioning and breaking-change policy: NEPSE has historically given notice in advance of breaking changes via email to the registered technical contact. Make sure that contact is monitored.

7. Realistic timeline

From the day you submit a complete application to the day you have working API keys, six to ten weeks is a fair planning estimate. The bottlenecks are typically (a) NEPSE's internal review queue, (b) coordinating signatures and payments on your side, and (c) the technical onboarding meeting if it has to be scheduled around month-end or quarter-end.

Plan integration work to happen in parallel with the application — build against the public endpoints first to de-risk the architecture, then swap the adapter layer to point at the licensed feed once keys land.

8. Common pitfalls

• Underestimating the redistribution clause. If your product shows data to users in any form (mobile app, web dashboard, B2B feed), confirm in writing whether your tier covers that — internal-only tiers are cheaper and a common upsell point at renewal.
• Skipping the legal review of the Data Access Agreement. Some clauses (data audit rights, termination on regulatory change, indemnity caps) are negotiable; some aren't. You only find out which is which by asking.
• Treating the security deposit as expensed. It's refundable — track it on the balance sheet, follow up at termination, don't write it off.
• Building against a single connection without a fallback. NEPSE's API does have downtime; have a polling fallback to your last-known-good cache.
• Forgetting the renewal date. Some teams have lost weeks of trading because nobody owned the renewal calendar.
• Sharing credentials across environments. NEPSE will trace abuse to your account and you don't want a developer's local script to trip the rate limit at quarter-end.

9. The unofficial-data alternative

If your use case doesn't justify the licensing budget (e.g. you're a single-person research project, a student dissertation, a stealth-mode startup proving the concept), the practical alternative is to consume NEPSE's public-facing web endpoints — the same ones that power nepalstock.com.np and aggregator sites. Be honest about the trade-offs:

• No SLA. Endpoints can change schema or disappear without notice.
• No contractual right. NEPSE could ask you to stop. Most projects never hear from them; some do.
• Likely rate-limited by IP. Plan polite request cadence and exponential backoff.
• Redistribution is murky. Showing NEPSE data on a non-commercial educational site is usually fine; building a paid product on it is not.

Most serious Nepali capital-markets products eventually license directly. The cleanest pattern we've seen: bootstrap on public endpoints, demonstrate traction with real users, then approach NEPSE with a concrete use case and a budget. The conversation goes much faster when you can point to an existing user base.

10. Contacts

Direct your initial enquiry to NEPSE's IT division at their head office, Singha Durbar Plaza, Kathmandu. The IT team handles technical fit and API provisioning; the Vendor Management / Administration division handles contracting and fees. The current phone numbers, dedicated email aliases, and the responsible contact person are listed in the official PDF — those rotate as NEPSE restructures, so verify before reaching out.

If you're submitting in person, allow a half-day at the office on submission day. Bring physical copies of every document plus a USB drive with a backup PDF set — NEPSE staff have asked for both in the past.

Closing thought

API licensing is one of those problems that looks bureaucratic from outside and turns out to be straightforward once you actually walk through it. The official PDF is short, the application form is one page, and the NEPSE team is responsive when you treat the process seriously. The teams that struggle are the ones that show up under-prepared and try to negotiate the schedule on the spot — go in with complete paperwork, a clear technical brief, and the right tier already chosen, and you'll have keys in your CI/CD pipeline before the quarter is out.