nepalstock.com APIwww.nepalstock.com ↗
Access live NEPSE trading data, market summaries, full securities listings, and per-stock price history via the nepalstock.com API. 4 endpoints, no login required.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/b3ba34ee-1ca5-437b-8dc4-d04c26ff409f/list_securities' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace nepalstock-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: NEPSE SDK — live market data and historical prices for Nepal Stock Exchange."""
from parse_apis.Nepal_Stock_Exchange__NEPSE__API import Nepse, NotFoundError
client = Nepse()
# List all listed securities on NEPSE
for security in client.securities.list(limit=5):
print(security.symbol, security.security_name)
# Get live trading data for all stocks in the latest session
quote = client.stock_quotes.list(limit=1).first()
if quote:
print(f"{quote.symbol}: LTP={quote.last_traded_price}, Change={quote.percentage_change}%")
# Drill into a specific security's historical data
security = client.securities.list(limit=1).first()
if security:
try:
for record in security.history(start_date="2026-06-15", end_date="2026-06-19", limit=3):
print(record.business_date, record.close_price, record.total_traded_quantity)
except NotFoundError as exc:
print(f"Security not found: {exc}")
print("exercised: securities.list / stock_quotes.list / security.history")
List all non-delisted securities (scrips) currently listed on NEPSE. Returns security ID, symbol, full company name, and active status for each security. Use the security ID from this endpoint to query historical data via get_stock_history.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer",
"securities": "array of security objects with id, symbol, security_name, active_status"
},
"sample": {
"data": {
"total": 563,
"securities": [
{
"id": 9192,
"symbol": "USHL",
"active_status": "A",
"security_name": "Upper Syange Hydropower Limited"
},
{
"id": 397,
"symbol": "ADBL",
"active_status": "A",
"security_name": "Agricultural Development Bank Limited"
}
]
},
"status": "success"
}
}About the nepalstock.com API
The nepalstock.com API exposes 4 endpoints covering every aspect of Nepal Stock Exchange market data: a full registry of listed securities, session-level market summary metrics, live daily trading statistics for all scrips, and paginated historical OHLC data per security. The get_live_trading endpoint alone returns last traded price, percentage change, previous close, and total traded quantity for every active security in the most recent session.
Securities and Market Coverage
The list_securities endpoint returns every non-delisted scrip currently listed on NEPSE, including each security's numeric id, symbol, security_name, and active_status. The id field is the key input for get_stock_history, so querying this endpoint first is the standard way to build a local symbol-to-ID map for the full exchange.
The get_market_summary endpoint returns session-level aggregate figures as a key-value map: total turnover, total traded shares, total transactions, total scrips traded, total market capitalization, and total float market capitalization for the most recent trading session.
Live and Historical Trading Data
The get_live_trading endpoint provides per-security statistics for the current or most recent session. Each record includes last_traded_price, percentage_change, previous_close, close_price, and total_traded_quantity — useful for building dashboards or screening for intraday movers across the full NEPSE universe.
For historical analysis, get_stock_history accepts a security_id, start_date and end_date (both in YYYY-MM-DD format), and an optional page_size. The response returns daily records with business_date, total_trades, total_traded_quantity, total_traded_value, high_price, low_price, and close_price, alongside a pagination object showing total_elements, total_pages, page_number, and page_size. Large date ranges can be walked using pagination controls.
The nepalstock.com API is a managed, monitored endpoint for www.nepalstock.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when www.nepalstock.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official www.nepalstock.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a NEPSE screener that flags securities where
percentage_changeexceeds a threshold usingget_live_trading. - Track daily market-wide turnover and capitalization trends over time using
get_market_summary. - Construct OHLC candlestick charts for any listed security using
get_stock_historywith custom date ranges. - Maintain a locally synced symbol registry for NEPSE by polling
list_securitiesfor new or delisted scrips. - Calculate rolling volatility for individual stocks using
high_priceandlow_pricefields fromget_stock_history. - Monitor total traded quantity alongside price change to identify unusual volume events via
get_live_trading. - Backtest simple trading strategies against NEPSE price history using paginated data from
get_stock_history.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does nepalstock.com have an official developer API?+
What does `get_stock_history` return and how do I retrieve data for a specific security?+
security_id (the numeric ID from list_securities), start_date, and end_date in YYYY-MM-DD format. Each record includes business_date, total_trades, total_traded_quantity, total_traded_value, high_price, low_price, and close_price. Use the optional page_size parameter and the pagination object in the response to walk through large result sets.Does `get_live_trading` distinguish between intraday snapshots and end-of-day figures?+
last_traded_price, percentage_change, and total_traded_quantity. Tick-level or intraday granularity is not currently available. You can fork this API on Parse and revise it to add an intraday endpoint if that data surface becomes available on the source.Does the API cover broker-level data, order book depth, or company fundamentals?+
How far back does the historical data go in `get_stock_history`?+
start_date and end_date freely. In practice, data availability varies by security age and exchange record-keeping, so very old scrips or recently listed ones may have shorter histories.