Insider Holdings

API TraderAPI QuantAPI Developer

Insider positions - what a director, officer or major holder holds in an issuer on a date - from the same official venues as the global transactions feed.

A position is a level, not a trade. It comes from a venue that publishes the position itself (Taiwan's month-end register), from a transaction notice that states the holding after the trade (Singapore, Indonesia, Korea, New Zealand), or from a roll-forward; the basis field says which. By default each insider's latest position on or before date is returned.

Available Data Points:

  • Country / Source Code: The market, and the official venue the row was read from (see the coverage endpoint). Rows from ORTEX's 2iQ insider history carry 2iq_ instead (2iq_jp, 2iq_gr, ...): they were not read from the venue.
  • Company / Ticker / Exchange Symbol / ISIN: The issuer as filed, and the ORTEX listing it resolved to. Ticker and exchange are blank where the filing named an issuer ORTEX has not matched yet.
  • Insider Name / Insider Role / Closely Associated: The reporting person and their role as filed. Closely associated marks a spouse, trust or controlled entity reporting under the manager's obligation. Some venues publish no name by law (Switzerland) or report by statutory body (Brazil); the field is then blank rather than invented.
  • Basis: statement, after_transaction or derived - see above.
  • As Of Date / Published At: The date the position is stated for, and when it became public.
  • Shares Held / Shares Before / Shares Pledged / Percent Held: The position, the position before the event where the same statement gives it, shares pledged as collateral, and the share of the class - each null where the venue did not state it.

Filtering

Supply country or insider_name; one issuer's holdings are /api/v11/stock/{namespace}/{identifier}/insiders/holdings/. date moves the snapshot back in time; history=true returns every statement instead of the latest one.

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

Query Params
string

Limit the result to one country, as an ISO 3166-1 alpha-2 code (case-insensitive). Omit it for every country covered. A code that is not covered returns 400 invalidCountry, whose message lists the codes that are valid.

date

Returns the most recent snapshot on or before this date (format yyyy-mm-dd; defaults to the latest available). On a stock path, a ticker resolves to the listing that held it on this date, so a renamed or reused ticker names the company it named then.

string

Insider name (case-insensitive substring match; EDGAR names read SURNAME FIRSTNAME).

boolean

true returns every stated position on or before date rather than only the latest one per insider. Default false.

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