Official short interest history

API Enterprise

Official short-interest history for a single instrument, for enterprise keys: the same rows as the retail endpoint, uncharged.

Official short interest is the short position reported by the exchange or regulator for a settlement date — FINRA in the United States, and the equivalent official feeds for Canada, Australia and Hong Kong. It is a disclosed figure, not a model.

It is not the ORTEX short-interest estimate served by the Short Interest endpoint. The estimate is daily and current; the official figure is published only on the market's reporting schedule (twice a month in the United States and Canada) and reaches the public roughly a week or more after the settlement date it describes. The two routinely differ, and a gap between them is information, not an error.

Available Data Points:

  • Settlement Date: The date the reported positions were measured at (YYYY-MM-DD format).
  • Published Date: The date the report was published. Use this rather than the settlement date when testing a strategy: the figure was not public before it.
  • Official SI Shares: The number of shares the exchange or regulator reported sold short at the settlement date. Split-adjusted to today's terms by default; pass split_adjusted=false for the figure as reported.
  • Official Avg Daily Volume: The average daily share volume over the reporting period, on the same basis as the shares.
  • Official Days to Cover: Official SI shares divided by average daily volume, as reported (a split does not change it).

Coverage

Listings in the United States, Canada, Australia and Hong Kong. Other markets publish no official short-interest figure of this kind, so a listing elsewhere returns an empty result (a 200 with meta.emptyReason); for European disclosures see the ESMA Positions endpoint.

Filtering

from_date and to_date are both required on this endpoint and bound the settlement date, inclusively. Results are ordered by settlement date, oldest first.

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]

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.

boolean
Defaults to true

Whether share counts — and, on the closing-prices endpoints, prices and volumes — are adjusted to today's terms (default) or returned as-was on the data date. Pass false for unadjusted (as-was) values.

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.

string
enum
Defaults to json

Response format. "json" (default) or "csv".

Allowed:
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

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