API Enterprise

The ETF money-flow aggregate: for every day in the window, the inflow, outflow, net flow, assets under management and fund count of each category within a classification group (asset class, geography, sector, size or strategy), for a region. This is the series the ORTEX money-flow page charts, served as rows.

Built for dashboards and macro work: one call returns a whole window rather than one day, the response is uncharged (no credits), and every figure is in USD so groups and regions compare directly.

A fund's daily flow is its NAV times the change in its shares outstanding, converted to USD on the day. Flows are summed per category over the share classes that carry the label; share-class assets are counted once, never alongside their parent fund. A day is written the morning after, and late-reporting funds keep landing for a day or two, so the most recent dates can still be filling in.

Available Data Points:

• Date: The trading date the flows are for (YYYY-MM-DD).
• Group: The classification dimension: asset_class, geography, sector, size or strategy.
• Category: The label within the group, e.g. Equity, Information Technology, Large Cap.
• Inflow: Sum of positive daily flows across the category's funds, USD. Never negative.
• Outflow: Sum of negative daily flows, USD. Stored signed, so never positive.
• Net Flow: Inflow plus outflow, USD.
• AUM: Sum of the category's net assets on the date, USD.
• Fund Count: Share classes that contributed to the row.

Region, group and window

region takes US (default), EUROPE or ALL - the three regions the aggregate is computed for; other region names and ISO-2 codes return 400 invalidRegion here even though the bulk endpoints accept them. group selects one classification dimension, or omit it for all five. from_date is required and to_date defaults to today. Rows are ordered by date, group and category.

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! Contact [email protected]