Content for a Stock

API Enterprise

ORTEX Market Intelligence content about one instrument — pulses, weekly digests, trader notes, earnings previews, convergence reports and market commentary — published inside a date window, newest first.

Content matches when the instrument is its primary subject or when its body mentions the instrument, so digests and commentary that referenced it in passing are included. Each row names its own primary instrument, which is not always the one you asked for.

Window

from_date and to_date are both required and bound the publication date (UTC). The rest of the feed's filters apply: content_type, pulse_type, theme, severity, topics, q and include. Access follows your key's region and date-window restrictions.

JSON only

Rows carry nested 'identifiers', 'provenance' and 'topics', so this endpoint returns JSON only.

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

Path Params
string
required

Where to find the instrument: a venue (exchange symbol, MIC or ISO-2 country) or an identifier scheme (tid, sid, cid, isin, figi). See Identifying an instrument.

string
required

The ticker on that venue, or the value in that scheme. An ISIN, sid, cid or share-class FIGI answers for the main listing only; reference/listings lists the others. See Identifying an instrument.

Query Params
date
required

Inclusive start of the returned date window. Required — a missing value returns 400 invalidDateRange. Also anchors instrument resolution: the instrument that owned the ticker at this date is the one the whole response describes. Format: YYYY-MM-DD.

date
required

Inclusive end of the returned date window. Required — a missing value returns 400 invalidDateRange. Format: YYYY-MM-DD.

string

Return only content of this type. The set of types grows over time, so this is an open vocabulary rather than a fixed list — an unrecognized value returns an empty result rather than an error.

string

Return only pulses of this sub-type. Applies to content_type=pulse rows.

string

Return only content carrying this theme (a row's theme value, such as overall or short_interest). Applies to digests and market commentary. These are Market Intelligence's own themes, not the business themes of reference/themes/catalog/. Named content_theme so it can't be mistaken for the Alt Data catalog's theme filter, which takes business theme names.

string

Return only content at this internal priority level. The value is not published on the row itself, so check the request block of the response to confirm the filter ORTEX applied.

string

Comma-separated topic slugs. Rows matching any requested topic are returned, so topics=short_interest,options reads as 'short interest or options'. A value naming no known topic returns an empty result rather than silently widening the response.

string

Free-text search across the headline and body. Supports quoted phrases and -exclusion the way a search engine does. Capped at 100 characters; anything longer is truncated rather than rejected.

string

Comma-separated list of optional fields to add to each row. Valid values: headline, body, provenance, pulse_type, theme, identifiers. Omitted by default because each costs a query or a Markdown render per row, and most callers listing content are building an index rather than reading the articles. Unrecognized names are ignored.

integer

Page number within the paginated result set. Must be >= 1. Defaults to 1.

integer

Number of rows per page. The default and the maximum allowed depend on the API tier; a value above the tier maximum is rejected with 400 invalidPageSize.

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json