Endpoint Migration
YONEPSE v2 uses folder-based JSON endpoints. Old flat paths expire after Nov 18, 2026.
Migration GuideWho We Are
We're My Wallet Team and Yoguru Team — two groups who got tired of digging through clunky market portals just to find basic NEPSE data. So we built YONEPSE: a clean layer between raw exchange data and the people who actually use it.
What We're After
Make NEPSE data accessible without friction. No logins, no paywalls, no “contact support for an API key.” Just files you can fetch, read, and drop into your own tools — plus a frontend that proves the data is useful, not just raw.
Version & System Status
YONEPSE v2 is the current version — folder-based endpoints, compact broker records, daily and intraday LTP shards, organized page assets, and automated data integrity checks before any update hits production.
Principles
- Canonical files grouped by domain
- Compact public fields over raw upstream payloads
- Legacy compatibility during migrations
Automation
Market data refreshes via scheduled GitHub Actions during trading hours. IPO, dividends, brokers, and reference data are maintained by scraper workflows.
Guardrails
JSON validity, OpenAPI YAML, data shapes, page paths, JS syntax, and Python compilation are checked before any automated data update is committed.
Use the published data freely for dashboards, research, or tools. Contributions, bug reports, and suggestions are always welcome.
Data Sources
YONEPSE aggregates public market data into stable files. Source attribution remains visible — this is a presentation layer, not an official exchange.