API Enterprise

The upcoming index review events ORTEX forecasts: one row per index per review, with its calendar, the ETF assets tracking the index, and the index's classification.

Only events still ahead of their effective date and either forecast or announced are returned. This is a view of what is coming, regenerated as reviews pass, not a history.

Available Data Points:

• Index Name: The index name — the value the detail endpoint accepts in indices.
• Index Family / Index Provider: The index series and the provider that reviews it.
• Status: Forecast before the provider announces the changes; Announced after.
• Rank Date: The provider's ranking cut-off: the date whose closing prices decide the review. Null when it is not known.
• Announcement / Trade / Effective Date: The review calendar.
• Comments: The review's description.
• ETF AUM / ETF Count: USD assets and number of ETFs tracking the index.
• Flagship: Whether the index is its provider's flagship benchmark.
• Strategy / Market / Region / Country / Size / Sector / Style / Theme: The index's classification.
• Available As Of Dates: The forecast dates held for the event — pass one to the detail endpoint.

Filtering

indices narrows the feed to named indices (see the index_list endpoint). from_date (required) and to_date bound the trade date; to_date defaults to the earlier of today and three months after from_date, as in v1. An event whose trade date is not yet scheduled is always included.

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]