API TraderAPI QuantAPI DeveloperIncluded with ORTEX Advanced
The policy rate of the Federal Reserve, the Bank of England and the Bank of Canada, day by day: the federal funds target range and the effective rate that trades inside it, Bank Rate, and the overnight rate target.
The policy rate is the first input to every discount rate, every floating-rate coupon and every bank's net interest margin. Held next to the inflation and labour datasets, it shows what the central bank did about the figures those datasets carry.
Each rate is the central bank's own published figure, on one row shape across the three.
Available Data Points:
- Period Date: The period the value describes — what the number is about (the valid clock).
- Published At: When the value first became knowable — when the publisher released it (the knowledge clock). Filter on this for anything where look-ahead bias would matter.
- Value: The numeric value, where the series has one.
- Value Text: The textual value, for categorical series such as a trial's status or phase.
- Unit: Unit of the value, e.g.
vehicles,percent,USD. - Value Type:
number,percent,currency,countortext. - Frequency: How often the publisher releases the series.
- Market: The market the reading describes — an ISO-3166 alpha-2 code (
DE), a sub-national one (US-CA), a supranational aggregate (EA,EU) orGLOBAL. - Series Slug: Which series the reading belongs to. Unique within a publisher, not globally.
- Series Name: Human-readable name of the series.
- Source Slug: Publisher/feed identifier, e.g.
kba_registrations. - Source Name: Human-readable name of the publisher or feed.
- Publisher: Who publishes the underlying data.
- Entity Ref: The publisher's own identifier for what the reading is about — a manufacturer name, a securitisation trust, a reactor unit, a country code. Kept so any value can be traced back to the row it was parsed from.
This dataset describes a market, not a company
Every reading here is about a country or a whole market, so there is no ticker in the path and no instrument in the response envelope. That is deliberate: attaching a national print to a listing would be a claim the data does not support. Read it as the context the company-level endpoints are measured against.
Coverage
Daily, as each central bank publishes it. The federal funds target range and the effective federal funds rate come from the Federal Reserve Bank of New York, Bank Rate from the Bank of England and the overnight rate target from the Bank of Canada. Percent, from 2000.
The Federal Reserve has set a target range since December 2008, and the upper and lower bound start then. The effective federal funds rate and the other two rates run from 2000.
What to look for
A policy rate is a step series: it holds between decisions and moves on the day one takes effect. The date of a change is the information, so look for the days the value differs from the day before.
fed_funds_effective is a traded rate, not a decision. It sits inside the target range and moves by a basis point or two between meetings; where it sits in the range is the reading.
Use market to pick one central bank: US, GB or CA.
Two dates on every reading, and the difference is the edge
periodDate is what the number is about. publishedAt is when it first became knowable. The gap between them is the whole point of alternative data — and it is also the trap. A Form 10-D describing July is filed in mid-August, so a backtest that treats the period as the knowledge date reads a document six weeks before it existed.
from_date and to_date filter on periodDate, because that is the axis you plot against. Join on publishedAt when you are joining against returns.
Filtering: one market or all of them
Called with no filters, the endpoint returns every series in the dataset, for every market ORTEX covers it in. Each row names its own market, seriesSlug and sourceSlug, so a single request is enough to chart the whole dataset.
Narrow it with any combination of market (one market), series (one measure) and source (one publisher). Filter values that are each valid but select nothing together return 400 invalidSelection rather than a misleading empty result.
How much history there is
Several of these publishers overwrite their own pages and keep no archive. Where that is so, the series begins on the day ORTEX started capturing it and lengthens from there — nobody, including the publisher, can supply the days before that. Everything ORTEX has ever fetched is archived on capture, so the series only ever grows.
Try it out! You can test the API with the trial key TEST. Simply include it in your request headers; either here, or add the header "Ortex-Api-Key": "TEST" to your http request.
Trial key restrictions: Trial keys may be limited to a specific date range and set of regions. Requests outside the allowed regions or entirely outside the allowed date range are rejected; a date window that partially overlaps the allowed range is trimmed to it, reported in meta.restriction.
Get full access! Get a key at app.ortex.com/apis
