KeyVex Insider Transactions API

The Insider Transactions API from KeyVex — 1 operation(s) for insider transactions.

GitHub OpenAPI

Operations 1

GET /v1/insider-transactions Returns executive insider transactions filed on SEC Form 4 — open-market… #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/keyvex-com:keyvex-com-insider-transactions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

keyvex-com-insider-transactions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: KeyVex Insider Transactions API
  version: 0.102.0
  termsOfService: https://keyvex.com/terms
  description: 'US public financial-disclosure data — congressional trades, insider filings (Form 4), lobbying, Treasury auctions, member profiles. Requires an API key — create a free one at https://keyvex.com and send it as the header `x-api-key: `. A free key returns most public-record datasets (one year of history; no market-price data and a few heavy datasets are on paid plans only), capped at 60 requests/day; paid plans raise the caps. The daily allowance resets at midnight Eastern.'
servers:
- url: https://api.keyvex.com
security:
- ApiKeyAuth: []
tags:
- name: Insider Transactions
paths:
  /v1/insider-transactions:
    get:
      operationId: get_insider_transactions
      summary: Returns executive insider transactions filed on SEC Form 4 — open-market…
      description: 'Returns executive insider transactions filed on SEC Form 4 — open-market purchases and sales by officers, directors, and 10%-owners of public companies. Each record is one transaction line item from one filing. Use this when the user asks about: insider buying or selling at a specific company, all recent insider activity across the market, transactions by a specific officer, or large insider trades by value. Form 4 is the fastest insider-trade signal in the public record — must be filed within 2 business days of the trade. The reporting_lag_days field tells you how stale a particular disclosure is. Returns BOTH non-derivative rows (direct common-stock buys/sells, RSU vests, grants, gifts, tax-withholding sales) AND derivative rows (option exercises, warrant conversions, RSU/PSU activity). Filter to one or the other with is_derivative; filter to specific transaction codes with transaction_codes. Common transaction codes: P open-market purchase | S open-market sale A grant / award / RSU vest | M exercise of derivative X exercise of in/at-the-money derivative | C conversion of derivative F payment of exercise price or tax with shares | G bona fide gift D disposition to issuer (forced) | I 401(k)/ESPP | V voluntary ⚠ shares and price_per_share are NULLABLE, and null does not mean zero. SEC permits either to be omitted — the price can live in a footnote, and the share count is genuinely undetermined on instruments that convert at a future price (a convertible note settling on a later VWAP). Those filings state a dollar amount instead, so such rows carry total_value with a null shares. Before 2026-08-18 they were dropped from this dataset entirely. Do not do arithmetic on either field without a null check, and do not read a null share count as a trade of nothing — read total_value. Useful filter combos: ⚠ transaction_codes=[''P''] IS NOT ''open-market buys''. SEC defines P as ''open market OR PRIVATE purchase'', and the code alone says nothing about whether the security is common stock. Verified 2026-08-14: FLUT''s code-P rows are $250M of Total Return Swaps (is_derivative=true) and ATTO''s are an $8.5M private placement. Both are correctly labelled in transaction_nature and security_title — but a screen filtered on the code alone ranks them top by size. transaction_codes=[''P''], is_derivative=false, include_non_open_market=false genuine open-market common-stock buys — the combination you almost always want transaction_codes=[''M'',''X''] option exercises (cash-out trigger) transaction_codes=[''A''] grants / RSU vests is_derivative=true all option/RSU/warrant activity is_derivative=false, transaction_type=''sell'', min_value=1000000 large open-market sells of common stock Optional include_baseline=true: also returns matching Form 3 initial- ownership records (the insider''s *starting* position when they first became an insider) under a `baselines` field. Use this when you need to know how big a sale is relative to the insider''s full position — Form 4 alone shows the delta, Form 3 anchors the baseline. Requires ticker or company_cik to be set. Baseline rows with is_nil_filing=true are ''no securities owned'' Form 3s (~half of all filings) — the insider filed but started with ZERO holdings; shares_owned 0 is the position, not missing data. A ticker search also returns rows this issuer FILED UNDER SYMBOLS IT NO LONGER LISTS — renames, filer typos and ADR spellings all split a company''s history across symbols. Each row keeps `ticker` exactly as SEC received it and gains `current_ticker` when the issuer trades under a different symbol today; the response carries `ticker_resolution` naming every symbol searched. Separately-listed share classes are NOT merged: GOOG does not return GOOGL. Asking for a RETIRED symbol returns only rows filed under it, because retired symbols get reissued to other companies. Rows found under a retired symbol are checked against the issuer''s CIK, so a symbol another company files under today cannot leak its rows in.'
      parameters:
      - name: ticker
        in: query
        required: false
        description: Stock symbol filter, e.g. 'AAPL'. Case-insensitive.
        schema:
          type: string
      - name: company_cik
        in: query
        required: false
        description: SEC CIK number (10-digit, padded with leading zeros). Alternative to ticker when known.
        schema:
          type: string
      - name: officer_name
        in: query
        required: false
        description: Full or partial officer name; case-insensitive substring match. Works on BOTH data_sources — `reporting_owner_name` is the same filter under its v2 name, and either spelling is accepted on either source; passing both with different values is rejected. A name of 1-2 characters (e.g. 'Li', 'Ng') matches as a whole word within the newest 5,000 rows in the sort order only, and the answer says so; reporting_owner_cik searches the full history.
        schema:
          type: string
      - name: transaction_type
        in: query
        required: false
        description: 'Filter by direction. ''buy'' means PURCHASED, not merely acquired: setting this parameter also switches include_non_open_market to false by default, so RSU vests, option exercises and other grants (transaction_nature=EQUITY_COMP) and gifts/transfers/equity swaps (NON_OPEN_MARKET_TRANSFER) are EXCLUDED. Without that default a ''buy'' screen is mostly vesting schedules — measured 2026-08-11 at 83% EQUITY_COMP, with a $6.3bn nano-cap grant topping the dollar-sorted results. ⚠ include_non_open_market=true does NOT widen a direction-filtered query, and this description used to say it did (''pass it to get the full ACQUIRED superset, grants included'') — corrected 2026-08-27 after the promise was measured against the behaviour. A direction is only ASSERTED for a genuine market trade: since 2026-08-17 the field is null for anything whose transaction_nature is not OPEN_MARKET, and for derivatives, because equity compensation is not buying (a Kyndryl new-hire grant had been ranking as $5.2M of insider buying at a discount to the market price). A row with no direction cannot match transaction_type=buy whatever include_non_open_market says. To see grants and transfers, OMIT transaction_type and filter on transaction_nature yourself — include_non_open_market widens exactly as documented there. Rows whose nature cannot be classified (INSUFFICIENT_DATA) always pass through where no direction filter is set, and are counted in unclassifiable_records_retained — unclassified is not the same as excluded. Works on BOTH data_sources. For legacy, this filters the stored field directly. For bulk_v2 (default), the field is derived per row from trans_code + trans_acquired_disp_cd (P→buy, S→sell, acqDisp=A→buy, acqDisp=D→sell, fallback A/M/X/C/I→buy else sell — same algorithm legacy uses); the v2 path pages through Firestore until enough matches are found and reports has_more accurately on the filtered set.'
        schema:
          type: string
          enum:
          - buy
          - sell
      - name: is_derivative
        in: query
        required: false
        description: Filter to derivative rows (options, RSUs, warrants, convertibles) when true, or non-derivative common-stock rows when false. Omit to see both. Works on BOTH data_sources — on bulk_v2 it maps to row_type ('deriv'/'nonderiv'); passing is_derivative and a conflicting row_type is rejected.
        schema:
          type: boolean
      - name: transaction_codes
        in: query
        required: false
        description: 'OR-filter on raw SEC transaction codes. Common picks: [''P''] open-market buys; [''S'',''F''] sells + tax-withholding; [''M'',''X''] option exercises; [''A''] grants/RSU vests; [''G''] gifts. Max 30 codes. Works on BOTH data_sources — `trans_codes` is the same filter under its v2 name, and either spelling is accepted on either source; passing both with different values is rejected. (comma-separated)'
        schema:
          type: string
      - name: min_value
        in: query
        required: false
        description: Filter to trades with total_value >= this amount (USD). Use to focus on large trades. Works on BOTH data_sources. On bulk_v2 the value is DERIVED per row exactly as the returned `total_value` field is — TRANS_TOTAL_VALUE where the SEC populated it (derivative rows), otherwise shares × price_per_share — so the filter and the field always agree. Rows carrying neither (no value and no shares/price) are EXCLUDED, since an unknown value cannot be shown to clear the threshold; that matches legacy — pass include_unpriced=true to keep them, and the response carries `min_value_note` saying so whenever min_value is set. Note this is a post-fetch filter on bulk_v2, so a very high threshold may return fewer rows than `limit` with has_more=true.
        schema:
          type: number
      - name: include_unpriced
        in: query
        required: false
        description: 'Only meaningful alongside min_value. By default a row that states NO price (price_check=''no_price_reported'') has no derivable total_value, cannot be shown to clear the threshold, and is EXCLUDED — correct, but it used to be silent, and ''cannot be shown to clear the threshold'' is not ''is below the threshold''. Measured 2026-09-09 at roughly 3 rows in 10,000, every one a filing where the insider genuinely stated no price rather than a data defect. Pass true to keep those rows in a min_value-filtered result; their total_value is null, so judge them on shares. Default false, which is exactly today''s behaviour. bulk_v2 only: passing it with data_source=''legacy'' is REJECTED rather than ignored, because a filter flag that silently does nothing is worse than one that is unavailable. Passing it without min_value is also rejected, for the same reason — nothing would be being excluded for it to re-admit.'
        schema:
          type: boolean
      - name: since
        in: query
        required: false
        description: ISO date (YYYY-MM-DD). Only records on or after this date, using sort_by as the date field.
        schema:
          type: string
      - name: until
        in: query
        required: false
        description: ISO date (YYYY-MM-DD). Only records on or before this date.
        schema:
          type: string
      - name: cursor
        in: query
        required: false
        description: 'Opaque pagination cursor. To read past `limit`, pass the `next_cursor` value from the previous response VERBATIM; the response omits next_cursor when there is nothing after this page. Keyset-based, not offset-based: the cursor names a position in the sort order, so filings that arrive while you page do not shift or duplicate rows beneath you. Works on BOTH data sources (bulk_v2 since 2026-08-08) — on bulk_v2 it names a position in the MERGED bulk + live-daily-feed stream, and both legs are advanced together. Keep sort_by/sort_order identical across a page sequence — a cursor issued under a different sort is REJECTED rather than silently applied to the wrong ordering. (`offset` and `page` are not supported and are rejected: an offset into this result is not an offset into either underlying source, and on the legacy store it would bill for every row it skipped.)'
        schema:
          type: string
      - name: sort_by
        in: query
        required: false
        description: 'Field used for ordering and for the since/until date filters. Default: disclosure_date. Validity differs by data_source: ''transaction_date'' works on BOTH; ''disclosure_date'' works on both (on the default bulk_v2 it maps to filing_date); ''total_value'' is LEGACY-ONLY — bulk_v2 rejects it, so to rank by trade size on bulk_v2 use min_amount to filter and sort by transaction_date instead.'
        schema:
          type: string
          enum:
          - disclosure_date
          - transaction_date
          - total_value
      - name: sort_order
        in: query
        required: false
        description: 'Default: desc (most recent / largest first).'
        schema:
          type: string
          enum:
          - desc
          - asc
      - name: limit
        in: query
        required: false
        description: Maximum records to return. Default 50, max 500.
        schema:
          type: integer
      - name: include_baseline
        in: query
        required: false
        description: When true, the response includes matching Form 3 initial-ownership records under a `baselines` field — lets you anchor Form 4 deltas to the insider's starting position. Requires ticker or company_cik. Default false. Works on BOTH data_sources (bulk_v2 accepted-but-ignored it until 2026-08-05).
        schema:
          type: boolean
      - name: merge_co_reports
        in: query
        required: false
        description: DEFAULT TRUE — leave it alone unless you specifically want raw filings. When shares are held through a fund, SEC requires the holding entity, its general partner AND the individual with investment control to each file their own Form 4 for the SAME purchase. By default those filings are merged into one row, so share counts and dollar totals are what actually traded; the row's officer_name names every filer and co_reported_accessions lists every accession. Set false to get one row per filing instead — useful for filing-level audit, but totals then double-count the transaction once per reporting person.
        schema:
          type: boolean
      - name: data_source
        in: query
        required: false
        description: 'Which backing collection to query. ''bulk_v2'' (DEFAULT as of 2026-05-24) = SEC quarterly bulk dataset, 2006q1 → the last PUBLISHED SEC quarter (SEC releases it ~2 weeks after quarter end; the live boundary is stated in coverage_warning). Footnote_refs[] inlined, aff10b5one present, full reporting_owners array, deeper coverage. Rows carry legacy field aliases for backward compat. On simple recency queries (descending, no v2-only filters) filings NEWER than the bulk boundary are automatically merged in from the live daily feed, so the default view stays current. ''legacy'' = daily EDGAR scraper output (insider_trades collection, no footnotes, no 10b5-1 flag). Its history runs from 2016 but is NOT continuous: measured 2026-11-03 against SEC''s own bulk copy, legacy holds ~0.3% of January 2022 through May 2024 and ~0.8% of December 2024 through March 2026, and is complete or nearly so for 2016-2021, June-November 2024 and from April 2026. Those are gaps in the scraper''s history, not in SEC''s data, and responses covering them carry a coverage_warning. (An earlier version of this description said ''2022+ only'', which was the inverse of the truth.) Use ''legacy'' ONLY when you specifically need the legacy document shape, or to browse post-boundary filings with filters the auto-merge can''t map. bulk_v2 (the default) is authoritative for coverage.'
        schema:
          type: string
          enum:
          - legacy
          - bulk_v2
      - name: reporting_owner_cik
        in: query
        required: false
        description: Reporting owner CIK (10-digit, zero-padded). bulk_v2 only — legacy uses officer_name substring instead.
        schema:
          type: string
      - name: reporting_owner_name
        in: query
        required: false
        description: 'Reporting owner name substring (case-insensitive). bulk_v2 only — legacy uses officer_name instead. IMPORTANT: name is matched client-side over a recent window, so it must be ANCHORED by ticker, company_cik, or reporting_owner_cik to search the full history — a name on its own only scans the most recent filings and can miss older trades (the response carries a coverage_warning when used unanchored). A name of 1-2 characters (e.g. ''Li'', ''Ng'') matches as a whole word within the newest 5,000 rows in the sort order only, and the answer says so; reporting_owner_cik searches the full history.'
        schema:
          type: string
      - name: row_type
        in: query
        required: false
        description: 'bulk_v2 only. Source-table discriminator: ''nonderiv'' for NONDERIV_TRANS rows (direct common-stock activity), ''deriv'' for DERIV_TRANS rows (options/RSUs/warrants). For legacy data, use is_derivative instead.'
        schema:
          type: string
          enum:
          - nonderiv
          - deriv
      - name: trans_codes
        in: query
        required: false
        description: OR-filter on raw SEC trans_code values (P, S, A, M, X, C, F, G, D, I, V, etc.). The v2 spelling of `transaction_codes` — same semantics, same codes; either spelling is accepted on either data_source and passing both with different values is rejected. Max 30 codes. (comma-separated)
        schema:
          type: string
      - name: aff10b5one
        in: query
        required: false
        description: bulk_v2 only. 10b5-1 trading-plan flag. '1' = plan adopted, '0' = no plan, '' = filer left the box blank (most common in 2023q1+ era), 'NOT_TRACKED' = pre-2023 era where the column did not exist on the SEC form. Filers often leave the box blank but disclose the plan in narrative footnotes — check footnote_refs[] for trans_code annotations.
        schema:
          type: string
          enum:
          - '1'
          - '0'
          - ''
          - NOT_TRACKED
      - name: schema_era
        in: query
        required: false
        description: bulk_v2 only. Form-version era. 'pre_2023' = filings made 2006q1 through 2022q4 (no AFF10B5ONE column). '2023_plus' = filings made 2023q1 onward (AFF10B5ONE column present, matches SEC Rule 10b5-1 amendment compliance date). Driven by FILING-quarter, not transaction_date — a late 2024 filing of an old 2009 trade still gets schema_era=2023_plus.
        schema:
          type: string
          enum:
          - pre_2023
          - 2023_plus
      - name: include_non_open_market
        in: query
        required: false
        description: 'Phase A v0.52.0 (2026-05-24): controls whether NON-MARKET events appear in the result. When false (the honest default for direction queries), the result keeps ONLY OPEN_MARKET rows (transaction_nature=''OPEN_MARKET'') plus INSUFFICIENT_DATA rows (passthrough — unclassified is not the same as confirmed-non-market, never silently dropped). It excludes BOTH NON_OPEN_MARKET_TRANSFER (gifts G, tax-withhold F, disposition-to-issuer D, will/inheritance W, voting-trust Z, tender U) AND EQUITY_COMP (grants A, exercises M/X/O, 401k/ESPP I, conversions C) — neither is a true open-market trade. Honest-by-default: when transaction_type=''buy''|''sell'' is set, defaults to FALSE; pass true to opt back in and see all natures. When transaction_type is NOT set, defaults to TRUE (returns everything, honestly tagged); pass false for a clean OPEN_MARKET+INSUFFICIENT_DATA view. The transaction_type field on each row is never mutated by this filter. The response envelope carries `unclassifiable_records_retained: N` when any INSUFFICIENT_DATA rows passed through, so the caller knows N of the returned rows couldn''t be classified.'
        schema:
          type: boolean
      responses:
        '200':
          description: 'JSON envelope: { results: [...], count, has_more }.'
        '400':
          description: Invalid parameter.
        '401':
          description: Missing or invalid API key.
        '402':
          description: This tool requires a higher plan (upgrade_required). Retrying will not help.
        '429':
          description: Tier rate/quota limit reached (rate_limited). Retry-After points at the reset.
      tags:
      - Insider Transactions
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key