How polymorphisma/nepse_scraper works
Nepse Scraper is a Python client for retrieving NEPSE market and company data. A user calls the public NepseScraper API; its market-data methods use a session to authenticate and make requests, then return decoded API responses. The client covers live, daily, historical, company, index, broker, and market-summary data, and supports registered custom endpoints. The session parses tokens and calculates request payload IDs with dedicated helpers. The feature areas are documented in the README; sampled client excerpts are incomplete, so internal wiring beyond the shown session calls is not inferred.
Main entry points: core.py API session · client.py NepseScraper · endpoints.py Endpoint catalog · auth.py Token parser
Components 15
Client API
- NepseScraper
nepse_scraper/client.py - Endpoint catalog
nepse_scraper/endpoints.py - Custom endpoints
nepse_scraper/client.py
Market Data
- Market status
nepse_scraper/client.py - Live data
nepse_scraper/client.py - Daily data
nepse_scraper/client.py - Historical data
nepse_scraper/client.py - Company details
nepse_scraper/client.py - Top stocks
nepse_scraper/client.py - Market summaries
nepse_scraper/client.py
Auth And Transport
- API session
nepse_scraper/core.py - Token parser
nepse_scraper/auth.py - Payload parser
nepse_scraper/auth.py
Other components
- Library user
- NEPSE API
Connections 16
- Library user → NepseScraper: calls
- NepseScraper → Endpoint catalog: reads
- NepseScraper → API session: initializes
- Custom endpoints → API session: calls
- Market status → API session: requests
- Live data → API session: requests
- Daily data → API session: requests
- Historical data → API session: requests
- Company details → API session: requests
- Top stocks → API session: requests
- Market summaries → API session: requests
- API session → Endpoint catalog: reads
- API session → Token parser: parses tokens
- API session → Payload parser: calculates IDs
- API session → NEPSE API: sends requests
- NEPSE API → API session: returns responses