US Government Trades

API Enterprise

Public securities transactions in one stock disclosed by members of the US government - congressional STOCK Act filings, executive-branch OGE Form 278-T reports and federal judges' periodic transaction reports.

Available Data Points:

  • Transaction Date: When the transaction was made (YYYY-MM-DD).
  • Report Date: The date on the filing that disclosed it (YYYY-MM-DD).
  • Published At: When the filing was observed publicly, as an ISO 8601 timestamp; null where only the report date is known. Use this rather than the transaction date when testing a strategy: filers have up to 45 days to disclose.
  • USD Value: The disclosed value band, e.g. $1001-$15000; a single figure where exact.
  • Transaction Type: The transaction type as disclosed, e.g. Buy, Sell, Sell (Partial), Exchange.
  • Filer Name: The official who filed.
  • Filer Photo / Filer Website: The filer's official portrait and website, where available.
  • Party: The filer's political party; empty for executive-branch and judicial filers.
  • Chamber: House, Senate, Executive or Judicial.
  • Branch: Legislative (House and Senate), Executive or Judicial.
  • Committees: The committees the filer sits on. For executive-branch filers this holds their agency, for judicial filers their court.

Filtering

from_date and to_date are both required on this endpoint and bound the transaction date. Results are ordered by report date, most recent first. The window filters on the transaction date, as v1 does - not on when the trade became public. A trade can be disclosed up to 45 days after it was made, so a backtest that must not see a trade before its disclosure should request a wider window and filter on publishedAt (or reportDate where publishedAt is null).

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.

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