Insiders Transactions

Provides transaction-level data and is more granular than /holders/insiders.

This endpoint returns a detailed, paginated list of insider transactions for a stock, including transaction descriptions, share counts, values, filer identity, and ownership type.

Asset Type Compatibility

  • Stocks: Returns insider transaction records based on reported filings.
  • ETFs and Mutual funds: Not applicable. Returns an empty result:
"result": {
        "total_count": 0,
        "items_count": 0,
        "items": []
}

This behavior is expected and does not indicate an error.

When to Use This Endpoint

  • Display a full insider trading history for a stock.
  • Power “Insider Transactions” tables and timelines.
  • Analyze insider behavior patterns (sales vs awards vs purchases).
  • Complement v1/holders/insiders (summary) with transaction-level detail.
  • Support compliance, governance, and transparency use cases.

Request Parameters

POST
v1/holders/insiders-transactions
symbol stringrequired

Asset identifier (ticker symbol). Must be a stock symbol.

filters arrayoptional

Optional filter expressions.

Each filter condition is defined as: [field, operator, value]. Conditions can be combined using logical operators and/or.

Supported operators:

Numeric fields:

  • > - greater than
  • >= - greater than or equal
  • < - less than
  • <= - less than or equal
  • = - equals
  • <> - not equal

String fields:

  • like – pattern match (requires % as a wildcard)
  • not_like - pattern does not match (requires % as a wildcard)
  • contains - value exists in string
  • not_contains - value does not exist in string
  • startswith - string starts with value
  • endswith - string ends with value

% usage examples:

  • %abc% - matches any string containing "abc"
  • abc% - matches any string starting with "abc"
  • %abc - matches any string ending with "abc"

Example:

"filters": [
    "shares",
    ">",
    10000
]
sort_by arrayoptional

Optional sorting configuration for result items. Each sorting setup is defined as [selector, desc]:

  • selector - Metric used for sorting (e.g., shares).
  • desc - Sorting direction (true for descending, false for ascending).

Sortings can be combined using ,.

Example:

"sort_by": [
    {
        "selector": "shares",
        "desc": false
    }
]
offset integeroptional

Pagination offset (0-based).

limit integeroptional

Maximum number of transaction records to return.

tag stringoptional

User-defined identifier for the task (max 255 characters).

It is returned in the response data object, allowing you to match results with the corresponding request. It does not affect API processing or filtering logic.

Example Request
curl --location "https://api.finimpulse.com/v1/holders/insiders-transactions" \
  --header "Content-Type: application/json" \
  --header "Authorization: Bearer <API_TOKEN>" \
  -d '{
      "symbol": "NVDA",
      "offset": 0,
      "limit": 3,
      "tag": "just tag"
  }'
using System.Net.Http;
using System.Net.Http.Headers;
using System.Text;

var client = new HttpClient();
var url = "https://api.finimpulse.com/v1/holders/insiders-transactions";

client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", "<API_TOKEN>");
client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));

var json = @"{
    ""symbol"": ""NVDA"",
    ""offset"": 0,
    ""limit"": 3,
    ""tag"": ""just tag""
}";
var content = new StringContent(json, Encoding.UTF8, "application/json");

var response = await client.PostAsync(url, content);
var result = await response.Content.ReadAsStringAsync();
Console.WriteLine(result);
<?php
$curl = curl_init();

curl_setopt_array($curl, [
  CURLOPT_URL => "https://api.finimpulse.com/v1/holders/insiders-transactions",
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_CUSTOMREQUEST => "POST",
  CURLOPT_HTTPHEADER => [
    "Content-Type: application/json",
    "Authorization: Bearer <API_TOKEN>"
  ],
  CURLOPT_POSTFIELDS => json_encode(
[
      "symbol" => "NVDA",
      "offset" => 0,
      "limit" => 3,
      "tag" => "just tag"
    ]
  )
]);

$response = curl_exec($curl);
curl_close($curl);

echo $response;
import urllib.request
import json

url = "https://api.finimpulse.com/v1/holders/insiders-transactions"
headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer <API_TOKEN>"
}
data = {
    "symbol": "NVDA",
    "offset": 0,
    "limit": 3,
    "tag": "just tag"
}

req = urllib.request.Request(url,
    data=json.dumps(data).encode("utf-8"),
    headers=headers,
    method="POST")

with urllib.request.urlopen(req) as response:
    result = json.loads(response.read().decode("utf-8"))
    print(result)
const https = require('https');

const data = JSON.stringify({
    "symbol": "NVDA",
    "offset": 0,
    "limit": 3,
    "tag": "just tag"
});

const options = {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer <API_TOKEN>',
    'Content-Length': Buffer.byteLength(data)
  }
};

const req = https.request('https://api.finimpulse.com/v1/holders/insiders-transactions', options, (res) => {
  let body = '';
  res.on('data', chunk => body += chunk);
  res.on('end', () => console.log(JSON.stringify(JSON.parse(body), null, 2)));
});

req.on('error', (e) => console.error(e));
req.write(data);
req.end();

Response

Returns pagination metadata and an array of insider transaction records.

Pagination Fields

total_count integer

Total number of insider transactions available.

items_count integer

Number of transactions returned in the current response.

items array

Array of insider transaction entries.

Insider Transaction Record Fields

shares integer

Number of shares involved in the transaction.

value number

Transaction value (currency units; may be 0 for non-cash events such as grants).

transaction_text string

Description of the transaction (e.g. sale, award, grant). Reflects the filing description and may include pricing details.

filer_name string

Name of the insider who filed the transaction.

filer_relation string

Insider’s role or relationship to the company (e.g. Director, Officer).

start_date string

Transaction or filing date.

ownership string

Ownership type under which the shares are held or transacted.

Possible values:

  • D — Direct ownership

    Shares are owned or transacted directly by the insider in their personal capacity.

  • I — Indirect ownership

    Shares are owned or transacted indirectly, typically through trusts, family members, controlled entities, partnerships, or investment vehicles. The insider has a beneficial interest but does not hold the shares in a personal account.

Example Response
{
    "task_id": "fa30960d-0a12-49a5-a0a7-3ad2a3cb1af9",
    "status_code": 20000,
    "status_message": "OK",
    "cost": 0.0014,
    "data": {
        "symbol": "NVDA",
        "limit": 3,
        "offset": 0,
        "filters": [
            "shares",
            ">",
            10000
        ],
        "tag": "just tag",
        "sort_by": [
            {
                "selector": "shares",
                "desc": false
            }
        ]
    },
    "result": {
        "total_count": 131,
        "items_count": 3,
        "items": [
            {
                "shares": 12728,
                "value": 2341117,
                "transaction_text": "Sale at price 183.93 per share.",
                "filer_name": "SEAWELL A BROOKE",
                "filer_relation": "Director",
                "start_date": "2025-12-02",
                "ownership": "I"
            },
            {
                "shares": 20000,
                "value": 2368377,
                "transaction_text": "Sale at price 116.99 - 118.87 per share.",
                "filer_name": "SHAH AARTI S",
                "filer_relation": "Director",
                "start_date": "2025-03-20",
                "ownership": "D"
            },
            {
                "shares": 24590,
                "value": 4425727,
                "transaction_text": "Sale at price 176.91 - 180.88 per share.",
                "filer_name": "ROBERTSON DONALD F JR",
                "filer_relation": "Officer",
                "start_date": "2025-12-19",
                "ownership": "D"
            }
        ]
    }
}

Notes

  • A single insider may have multiple transaction records across time.
  • The same insider can appear with both Direct (D) and Indirect (I) ownership types.
  • Dates reflect filing timelines and may differ slightly from execution dates.