sysstra-data
Lightweight, generalized market data client for the Sysstra trading platform. Wraps sysstra-data-services with a typed, domain-namespaced Python interface.
Install
pip install sysstra-data
Quickstart
from sysstra_data import SysstraData
client = SysstraData(api_key="sk-...")
# Equities
eod = client.equities.eod("SBIN", "2025-01-01", "2025-06-30", exchange="XNSE")
intraday = client.equities.candles("SBIN", "2025-01-01", "2025-01-02", interval=5)
# Futures & Options
futures = client.futures.candles("NIFTY", "2025-01-01", "2025-01-31")
options = client.options.candles("BANKNIFTY", "2025-01-01", "2025-01-31",
option_type="CE", strike=48000)
chain = client.options.chain("BANKNIFTY", date="2025-01-15")
# Crypto & Forex
btc = client.crypto.candles("BTCUSDT", "2025-01-01", "2025-01-02", interval="1h")
eurusd = client.forex.candles("EURUSD", "2025-01-01", "2025-01-02", interval="1h")
# Reference data
exchanges = client.market.exchanges(market="IN")
symbols = client.market.symbols(exchange="XNSE", query="RELIANCE")
# Fundamentals
fii_dii = client.fundamentals.fii_dii("2025-01-01", "2025-01-31")
# Account (your own key/credits only)
me = client.account.me()
keys = client.account.list_keys()
A process-wide default client is also available for scripts that only need one:
import sysstra_data as sd
sd.set_api_key("sk-...")
candles = sd.equities.eod("SBIN", "2025-01-01", "2025-06-30")
Error handling
Every non-2xx response raises a specific exception, all subclassing SysstraDataError:
| Exception | Meaning |
|---|---|
SysstraAuthError |
Missing/invalid API key, or insufficient privilege |
SysstraValidationError |
Bad request shape |
SysstraSymbolNotFoundError |
Symbol doesn't exist |
SysstraAmbiguousSymbolError |
Symbol resolves to multiple exchanges — .candidates lists them |
SysstraInsufficientCreditsError |
Account is out of API credits |
SysstraServiceUnavailableError |
Backend reference/warehouse store unreachable |
SysstraConnectionError |
Network-level failure (timeout, DNS, SSL) |
SysstraAPIError |
Any other non-2xx response — carries .status_code |
Not yet implemented server-side
A few methods exist on the client for API symmetry but raise NotImplementedError
until sysstra-data-services grows the matching route: options.greeks(),
equities.announcements(), equities.fundamentals(),
fundamentals.earnings_calendar(), fundamentals.earnings_transcript().
Development
pip install -e ".[dev]"
pytest tests/ --ignore=tests/test_uat_integration.py
tests/test_uat_integration.py boots a real sysstra-data-services instance
in-process and needs that package importable plus a provisioned test API key.
License
MIT
Metadata
Release files for sysstra-data 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sysstra_data-0.1.2.tar.gz | 15.2 kB | Without provenance | Details for sysstra_data-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sysstra_data-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for sysstra_data-0.1.2-py3-none-any.whl |
Total release size: 30.2 kB
Release files / sysstra_data-0.1.2.tar.gz
| Download URL | sysstra_data-0.1.2.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
072f2ee6768786ee4165f27c7d886f6c2592260a4c4a39201af8321a02543382
|
|
BLAKE2b-256 checksum How to use checksums |
aa1b98e2c33bb11a8a96ece6763fe6987d0ad577b06f4515999f5e1beb97725e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / sysstra_data-0.1.2-py3-none-any.whl
| Download URL | sysstra_data-0.1.2-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5fe318f68868e905cdb0e8d747c33a0cb7350d1bc95edb0c8041c9fc1be72e3
|
|
BLAKE2b-256 checksum How to use checksums |
deca85cb77fde04423052f428fa81494206d1c6a8f25f9a6b23796cc2f5f0d2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for sysstra-data 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.