API Enterprise

Weekly per-company Stock Reports — long-form analytical write-ups generated from ORTEX data, delivered as Markdown. Returns the published feed, newest first. One company's report is /api/v11/enterprise/stock/{namespace}/{identifier}/market_intelligence/stock_reports/.

Enterprise keys receive the full article body. There is no premium gate and no truncation on this surface.

Available Data Points:

• Headline: The report's title.
• Summary: A short executive summary, two or three sentences.
• Body: The full article as Markdown.
• Ticker: The ticker of the company's primary listing at the time the report was generated.
• Exchange: The exchange symbol of that primary listing.
• Company Name: The name of the company the report covers.
• Ortex Company ID: Unique id for the company the report covers — the key for joining a report to any other ORTEX dataset. Reports are keyed on the company, so no listing or security id is given.
• Identifiers: The primary listing rendered with exchange, ticker, MIC and ISIN. At most one entry.
• Version: Bumped each time the report is regenerated for this company, so you can detect a revision.
• Published At: When the report went live. The only customer-facing timestamp on this surface.
• Provenance: How the report was produced — the generation audit, minus internal-only detail.

One report per company

Stock Reports are keyed on the company, not the listing: re-listings, dual listings and multiple share classes all share a single report. A report is regenerated in place rather than published as a new row each week, which is why there is no date range on this endpoint and why 'version' is how you tell revisions apart.

Visibility

Only published reports are returned. A report scheduled for a future date, or with no publication date set, is not visible until its publication moment arrives.

JSON only

A report row carries a Markdown body and nested objects, which CSV cannot represent, so this endpoint is JSON only — a CSV request returns 406 Not Acceptable.

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 date range and a set of regions. This feed takes no date parameter: a key whose allowed range ends before today is rejected, and rows published before the start of the range are left out, with the range served reported in meta.restriction. A region-limited key sees only rows whose listing is in an allowed region; naming an instrument outside them is rejected with 403 restrictedRegion.

Get full access! Contact [email protected]