P-Invertor API

Use the dashboard and predictor data directly in another app—without screen scraping.

API base: Loading…

GET/api/pages/index

Every figure on the Overview tab's market cards, for either market and any of the three period toggles — indices, FX and commodities, capital and fund flows, sector scores, breadth, timing signals, VIX, fear & greed, and bonds.

The response's as_of field is the snapshot timestamp — use it to tell fresh data from cached. This endpoint only ever reads the published snapshot; to make it produce newer numbers, queue a refresh (below).

GET/api/market-trends/{view}

The Overview tab's five research sub-tabs. Each name below is the {view} value, so all five share one URL shape.

Every response carries status and latest_metric_date. A status other than ok/cached means the trend pipeline has not published recently — check latest_metric_date before treating the numbers as current. Any other {view} returns 404.

Refreshing Overview data

The read endpoints above always serve the last published snapshot; they never scrape on demand. To produce newer data, queue a refresh — one call re-runs everything on the Overview tab: the market snapshot behind the 5/20/60-day toggles, and all five trend sub-tabs.

A refresh takes a few minutes end to end, and concurrent requests collapse into a single run. Poll /api/refresh-data/status rather than calling /api/refresh-data repeatedly.

Private personal-data API

For your own analysis applications only. Send the private key in X-API-Key; never place it in browser code.

GET/api/pages/predictor/{symbol}

Returns a stock’s current technical figures and, by default, the chart-ready OHLCV and indicator series.

Integration notes

Browser integrations are allowed by default. To restrict which browser apps may call the API, set CORS_ALLOW_ORIGINS to a comma-separated allowlist on the API deployment.

Predictor snapshots use the built-in default profile. Personal browser-only profiles, peer lists, custom signals, and interactive backtest inputs are not shared because they are user-specific.

For the interactive schema and every available endpoint, open API documentation.