quantjourney-api
Python SDK for the public/product qj-api contract.
Canonical package metadata:
| Field | Value |
|---|---|
| Repository | _repo_qj_api_sdk |
| Distribution | quantjourney-api |
| Python import | qj.api |
| Runtime client | QJ |
| Backend boundary | qj-api / https://api.quantjourney.cloud |
| Version | 0.1.5 |
| Git tag | api-v0.1.5 |
quantjourney-api is the public product/API SDK. The quantjourney umbrella
package lives in packages/quantjourney and installs quantjourney-api.
from qj.api import QJ, QuantJourneyAPI
qj = QJ.from_env()
health = qj.health()
capabilities = qj.capabilities()
# Provider connectors through qj-api
profile = qj.fmp.get_company_profile(symbol="NVDA")
gdp = qj.fred.get_series(series_id="GDP")
filings = qj.sec.get_recent_filings(limit=5)
trades = qj.massive.get_stock_trades(ticker="AAPL", limit=100)
legacy_quotes = qj.polygon.get_stock_quotes(ticker="AAPL", limit=100)
cpi = qj.tradingeconomics.get_historical_indicators(
country="United States",
indicator="Consumer Price Index CPI",
)
macro_revision = qj.dbnomics.get_series(
provider_code="ECB",
dataset_code="EXR",
series_code="D.USD.EUR.SP00.A",
revision="<commit-sha>",
)
# Research-source expansion (requires a backend with these routes deployed)
approvals = qj.openfda.get_drug_approvals(search='sponsor_name:"PFIZER"', limit=5)
attention = qj.apewisdom.get_mentions(filter="all-stocks")
pageviews = qj.wikimedia.get_pageviews(article="Apple_Inc.")
fear_greed = qj.alternative.get_fear_greed(limit=30)
dvol = qj.deribit.get_dvol(currency="BTC")
fees = qj.defillama.get_protocol_fees(protocol_slug="aave", data_type="dailyRevenue")
put_call = qj.cboe.get_put_call_ratios()
positioning = qj.cftc.get_net_positioning(symbol="VIX")
morpho_markets = qj.morpho.get_markets(chain_ids=[8453], limit=5)
bund_yield = qj.bundesbank.get_series()
# Provider-agnostic domain routes
routes = qj.domains.list()
prices = qj.domains.equity.pricing.get_historical_prices(symbol="NVDA")
# Product API surfaces
analytics = qj.analytics.registry()
ratios = qj.ratios.available(source="eod")
indicators = qj.technical.available()
# Compatibility aliases
qj2 = QuantJourneyAPI.from_env()
Local smoke from this checkout:
python scripts/qj_api_smoke.py --env .env
python scripts/endpoint_matrix.py --env .env
python scripts/endpoint_matrix.py --env .env --list
python scripts/endpoint_matrix.py --env .env --group connectors --allow-failures
python scripts/endpoint_matrix.py --env .env --group connector_examples --include-connector-examples --allow-failures
python scripts/connector_matrix.py --env .env
scripts/connectors.json stores one smoke example per connector. The endpoint
matrix verifies every connector route; connector_matrix.py runs the examples
and prints a compact result table.
The September research-source expansion adds openfda, apewisdom,
wikimedia, alternative, quiver, ember, opensky, manifold, deribit,
mempool, blockscout and blockchain, plus DefiLlama fee/revenue methods.
Calls use the normal QJ tenant/scopes and credentials. Configure upstream
Quiver and Ember keys in QJ Data Sources; do not send them as SDK method
parameters. Provider data remains in the response's value envelope.
Environment variables:
| Variable | Purpose |
|---|---|
QJ_API_URL |
qj-api base URL, default https://api.quantjourney.cloud |
QJ_API_TOKEN |
bearer token |
QJ_AUTH_URL |
qj-auth base URL for token exchange |
QJ_API_KEY |
QJ_live_* API key used to mint QJ_API_TOKEN |
QJ_API_CLIENT_ID |
service account client id for client_credentials |
QJ_API_CLIENT_SECRET |
QJ_svc_* service secret for client_credentials |
QJ_API_TENANT_ID |
optional tenant projection |
QJ_API_TEAM_ID |
optional team projection |
Install from PyPI:
pip install quantjourney-api==0.1.5
quantjourney-common-sdk is installed automatically as a dependency. Local
development can still use editable path installs for sibling checkouts.
The new surface keeps the smaller qj.api namespace, uses
quantjourney-common-sdk for
auth/transport, exposes dynamic qj-api connector clients, and keeps warehouse
data-plane concerns in quantjourney-data.
Release history
This history covers quantjourney-api (qj.api). The older quantjourney
distribution has its own version history. Dates below are the original PyPI
publication dates; these notes were added retrospectively from the release tags.
0.1.5 — 2026-09-08
- Added Twelve Data global market-data access.
- Added cost-guarded Databento historical and batch workflows.
0.1.4 — 2026-09-08
- Added Morpho Blue lending-market data and official Deutsche Bundesbank time series.
- Added market-wide CBOE put/call ratios and derived CFTC net positioning.
0.1.3 — 2026-09-06
- Added named SDK connector clients for openFDA and Quiver, covering FDA records and political disclosures through QJ API.
- Added ApeWisdom, Wikimedia and Alternative.me clients for market attention, pageviews and crypto sentiment.
- Added Ember, OpenSky and Manifold clients for electricity data, aviation activity and prediction markets.
- Added Deribit, mempool.space, Blockscout and Blockchain.com clients for crypto volatility and on-chain data.
- Added connector smoke examples and forwarding tests; documented the new DefiLlama fee/revenue methods with an SDK example.
- Documented QJ tenant/scope requirements and Data Sources configuration: Quiver and Ember require provider keys, while openFDA supports an optional key.
0.1.2 — 2026-08-16
- Added named SDK clients and smoke examples for USAspending, SAM.gov and Congress.gov.
- Added named Massive and Polygon clients, with examples for stock trades and quotes.
- Added TradingEconomics access and a historical macro-indicator example using provider keys configured in QJ.
- Added forwarding regression coverage for the new clients and existing DBnomics series/revision routes; updated usage examples.
0.1.1 — 2026-07-11
- First PyPI release of the separate
quantjourney-apidistribution, using theqj.apinamespace andQJclient. - Included dynamic provider clients, domain discovery/calls and product API clients for analytics, Backtester, universe, ratios, technical indicators and insider data.
- Used
quantjourney-common-sdkfor shared authentication and HTTP transport, including bearer tokens, user API keys, service credentials and tenant/team context. - Included connector and endpoint smoke scripts and configured GitHub Actions trusted publishing to PyPI.
Metadata
Release files for quantjourney-api 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| quantjourney_api-0.1.5.tar.gz | 12.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quantjourney_api-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.9 kB
Release files / quantjourney_api-0.1.5.tar.gz
| Download URL | quantjourney_api-0.1.5.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2a4448d7ca394473edee805963984608dc6debe41570b0db33ba1b7ecc0890e
|
|
BLAKE2b-256 checksum How to use checksums |
d28fec47b506635626f2669a33da0b810c1ad692eb7c188c56de4acf2817d257
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / quantjourney_api-0.1.5-py3-none-any.whl
| Download URL | quantjourney_api-0.1.5-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee2985168b42284a772471693ef4faa59b271f5d137ba0954dbeaf6396bccf87
|
|
BLAKE2b-256 checksum How to use checksums |
ecfb1f1f44e4e5fcc40a036956bf7389410b724e2bfc9998bc186816d6a9626c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency log