Form 144 API - Restricted Sales Notifications

Use the /form-144 endpoint, which returns Form 144 filings—the notices corporate insiders file before selling restricted or control securities. To pull the most recent planned-sale notices for one company, filter on the issuer's stock ticker, which is recorded both on the issuer object (issuerInfo.issuerTicker) and on the subject company entry in the entities array (entities.ticker). For example, set the ticker to GE for General Electric or HSY for Hershey.

Results are sorted by the filing acceptance timestamp (filedAt) in descending order by default, so the newest notices come back first. Each result carries the company name (issuerInfo.issuerName), the person whose account the shares are being sold from (issuerInfo.nameOfPersonForWhoseAccountTheSecuritiesAreToBeSold), and the planned sale details (securitiesInformation).

Use the /form-144 endpoint and filter on the company's Central Index Key, the unique identifier the SEC assigns to each filer. The issuer CIK appears on the issuer object (issuerInfo.issuerCik) and is also present in the entities array on the subject company entry (entities.cik). For example, the value 47111 identifies Hershey and 40545 identifies General Electric.

Because every Form 144 lists the subject company and the reporting person as separate entries in the entities array, filtering on the issuer CIK specifically (issuerInfo.issuerCik) targets the company rather than the insider. Results are returned newest-first by filing date (filedAt).

Use the /form-144 endpoint and filter on the accession number, the unique identifier EDGAR assigns to each filing (accessionNo), for example 0001950047-25-002675. Each accession number maps to exactly one Form 144 filing, so this returns a single record.

The response includes the full filing object—the form type (formType), the filing timestamp (filedAt), the issuer and reporting person details, the securities planned for sale (securitiesInformation), and any sales reported in the prior three months (securitiesSoldInPast3Months).

Use the /form-144 endpoint and filter on the filing acceptance timestamp (filedAt), which records when EDGAR accepted the filing, for example 2024-05-15T16:17:15-04:00. To restrict results to a window, the value of filedAt should fall between a start date and an end date, such as on or after 2024-01-01 and on or before 2024-12-31.

Results are sorted by filedAt in descending order by default. To page through a large date range, advance the from offset across requests while keeping size at its maximum of 50.

Use the /form-144 endpoint and filter on the aggregate market value of the securities to be sold (securitiesInformation.aggregateMarketValue), which is the total intended sale value, typically the unit price multiplied by the number of units. To find sizable planned sales, the value of this field should be greater than your chosen threshold, such as greater than 1000000 for sales above one million dollars.

Note that securitiesInformation is an array, so a single filing can list more than one block of securities—for example separate Class A and Class C entries—each with its own aggregateMarketValue. A filing matches when any entry meets the threshold.

Use the /form-144 endpoint and sort results by the aggregate market value of the securities to be sold (securitiesInformation.aggregateMarketValue) in descending order, which places the highest-value planned sales first. The sort parameter controls the ordering field and direction, overriding the default sort by filing date.

To focus the ranking, combine the sort with a query—for example restricting to a single company by its issuer CIK (issuerInfo.issuerCik) or to a date range on filedAt. Each result reports the intended number of units (securitiesInformation.numberOfUnitsToBeSold) alongside the dollar value.

Use the /form-144 endpoint and filter on the relationship between the selling person and the issuer (issuerInfo.relationshipsToIssuer). The filing instructions suggest values such as Officer, Director, 10% Stockholder, and Member of immediate family of any of the foregoing, though other descriptions appear as well—for instance Affiliate.

To isolate one group, the value of issuerInfo.relationshipsToIssuer should match the relationship you want, such as Director for board members or Officer for executives. Because the field is free text, allow for variant phrasings when the underlying relationship is the same.

Use the /form-144 endpoint and filter on the Standard Industrial Classification code of the subject company (entities.sic), which identifies the company's primary industry. For example, 7372 covers prepackaged software and 3674 covers semiconductors and related devices.

The SIC code is recorded on the subject company entry inside the entities array, and in the sample data it can appear with a trailing description, such as 7372 Services-Prepackaged Software. Filtering on the numeric code returns Form 144 filings across every company in that industry.

Use the /form-144 endpoint and filter on the issuer's state of incorporation (entities.stateOfIncorporation), recorded on the subject company entry in the entities array as a two-letter code, such as DE for Delaware, OH for Ohio, or NY for New York.

Set the value of entities.stateOfIncorporation to the state code you want. Note this is the legal state of incorporation, which is distinct from the issuer's mailing address state (issuerInfo.issuerAddress.stateOrCountry).

Use the /form-144 endpoint and filter on the form type (formType). Original notices carry the value 144, while amendments carry 144/A. To see only amendments, the value of formType should be 144/A; to see only originals, it should be 144.

An amendment corrects or updates a previously filed Form 144. Filtering on formType lets you study the two populations separately—for example, to count how often insiders revise their planned-sale notices.

Use the /form-144 endpoint. When a filing is an amendment (its form type is 144/A), the accession number of the filing it corrects is recorded in the reference-to-prior-filing field (previousAccessionNumber).

To retrieve the original notice, take the value of previousAccessionNumber from the amendment and query the /form-144 endpoint again, filtering on the accession number (accessionNo) equal to that value. This returns the original Form 144 so you can compare it against the amendment.

Use the /form-144 endpoint and filter on the SEC file number, the identifier used to track filings tied to the same registration. It appears on the subject company entry in the entities array (entities.fileNo) and on the issuer object (issuerInfo.secFileNumber), for example 001-00183 for Hershey or 001-35451 for MACOM Technology Solutions.

Set the value of entities.fileNo or issuerInfo.secFileNumber to the file number you want. Both fields carry the same identifier in the sample data, so either targets the filings for that registration.

Use the /form-144 endpoint and filter on the name of the individual on whose behalf the securities are being sold (issuerInfo.nameOfPersonForWhoseAccountTheSecuritiesAreToBeSold), for example Russell Stokes or CHRISTOPHER JOYCE.

Note that the reporting person also appears as an entry in the entities array (entities.companyName), often suffixed with (Reporting), and that name formatting can vary in capitalization and word order across filings. When searching by name, allow for those variations to capture every notice for the same person.

Use the /form-144 endpoint and filter on the name of the broker or market maker handling the sale (securitiesInformation.brokerOrMarketMakerDetails.name), for example Fidelity Brokerage Services LLC, J.P. Morgan Securities LLC, or Morgan Stanley Smith Barney LLC Executive Financial Services.

Because securitiesInformation is an array, a filing can list more than one block of securities, each with its own broker details. The broker's address is also available (securitiesInformation.brokerOrMarketMakerDetails.address) if you need to narrow by location.

Use the /form-144 endpoint and filter on the title or class of the securities to be sold (securitiesInformation.securitiesClassTitle), for example Class A Common Stock, Class C Capital Stock, or simply Common.

A single filing can plan sales across more than one class, with securitiesInformation holding a separate entry per class. The same class title also appears on each block of securities being sold (securitiesToBeSold.securitiesClassTitle). Note that class titles are free text and vary in wording and capitalization across filings.

Use the /form-144 endpoint and filter on the name of the exchange where the transaction is to be executed (securitiesInformation.securitiesExchangeName), for example NYSE, NASDAQ, or OTC Markets.

This field is free text, so the same venue can appear under different labels—for instance NYSE, New York, and NEW YORK all refer to the New York Stock Exchange in the sample data. When filtering by exchange, account for these variant spellings.

Use the /form-144 endpoint and filter on the nature of the acquisition transaction for the securities to be sold (securitiesToBeSold.natureOfAcquisitionTransaction), which describes how the insider obtained the shares. Values tied to equity compensation include Restricted Stock Units, Vested Restricted Stock Units, Restricted Stock Vesting, RSU Vest, and Performance Stock Units.

The securitiesToBeSold array can hold several entries, each describing a separate acquisition lot with its own nature description. The supporting fields natureOfPayment and nameOfPersonFromWhomAcquired add context—compensatory awards are commonly acquired directly from the issuer.

Use the /form-144 endpoint and filter on the gift flag for the securities to be sold (securitiesToBeSold.isGiftTransaction). When the shares were acquired as a gift, the value of this boolean is true.

For gifted securities, the date the donor originally acquired the shares is recorded separately (securitiesToBeSold.donorAcquiredDate), which matters for the Rule 144 holding period since the donor's holding time can carry over. The party the shares came from is also captured (securitiesToBeSold.nameOfPersonFromWhomAcquired).

Use the /form-144 endpoint and compare the date the securities were acquired (securitiesToBeSold.acquiredDate) against the approximate planned sale date (securitiesInformation.approxSaleDate). A long gap between the two indicates the insider held the shares for an extended period—for example, shares acquired in 2006 and planned for sale in 2025.

The /form-144 endpoint does not compute this gap for you; retrieve both date fields and measure the interval after the response is returned. Because securitiesToBeSold can list several acquisition lots, each lot's acquiredDate should be checked against the planned sale date.

Use the /form-144 endpoint and filter on the flag indicating no securities were sold in the past three months (nothingToReportFlagOnSecuritiesSoldInPast3Months). When the insider reports no prior sales, the value of this boolean is true.

When this flag is true, the array of prior sales (securitiesSoldInPast3Months) is typically absent from the filing. When it is false, that array is populated with the details of the recent sales.

Use the /form-144 endpoint and read the array of securities sold in the past three months (securitiesSoldInPast3Months). Each entry records one prior sale, with the number of units sold (securitiesSoldInPast3Months.amountOfSecuritiesSold), the gross proceeds raised (securitiesSoldInPast3Months.grossProceeds), the sale date (securitiesSoldInPast3Months.saleDate), and the share class (securitiesSoldInPast3Months.securitiesClassTitle).

Each entry also carries the seller's name and address (securitiesSoldInPast3Months.sellerDetails). This array is present only when the no-prior-sales flag (nothingToReportFlagOnSecuritiesSoldInPast3Months) is false.

Use the /form-144 endpoint and read the array of securities sold in the past three months (securitiesSoldInPast3Months). Each entry reports the gross proceeds from one sale (securitiesSoldInPast3Months.grossProceeds). Summing grossProceeds across every entry in that array gives the total cash the insider raised from recent sales reported on that notice.

The /form-144 endpoint does not return this total directly; retrieve the array and add the per-sale proceeds after the response is returned. The array is populated only when the no-prior-sales flag (nothingToReportFlagOnSecuritiesSoldInPast3Months) is false.

Use the /form-144 endpoint and inspect the plan adoption dates on the notice signature (noticeSignature.planAdoptionDates). When this array is present and holds one or more dates, the sale is being made under a pre-arranged trading plan, with each date marking when a plan was adopted.

A second signal sits in the prior-sales array: the seller name (securitiesSoldInPast3Months.sellerDetails.name) sometimes contains the text 10b5-1, the SEC rule that governs pre-arranged trading plans—for example 10b5-1 Sales Plan for RAJEEV RAJAN. Filtering for that text in the seller name surfaces sales executed under such plans.

Use the /form-144 endpoint and compare the number of units to be sold (securitiesInformation.numberOfUnitsToBeSold) against the total units outstanding for the issuer (securitiesInformation.noOfUnitsOutstanding). Dividing the planned units by the units outstanding gives the fraction of the company's stock the sale represents.

The /form-144 endpoint does not compute this ratio; retrieve both fields from each securitiesInformation entry and calculate it after the response is returned. This ratio is also relevant to Rule 144's volume limitation, which caps an affiliate's three-month sales at the greater of one percent of outstanding shares or the average weekly trading volume.

Use the /form-144 endpoint and inspect the signature text on the notice (noticeSignature.signature). When a notice is filed on the insider's behalf, the signature names a representative and contains phrasing such as attorney-in-fact for or as agent—for example /s/ J.P. Morgan Securities LLC as agent and attorney-in-fact for Charles Bland. Directly signed notices instead show the insider's own name.

The signature is free text, so filtering on terms like attorney-in-fact or as agent within noticeSignature.signature surfaces notices submitted by brokers or other representatives.

Use the /form-144 endpoint and read the remarks field (remarks), which holds any additional comments the filer added to the notice. For example, a remark may explain that the shares to be sold were acquired upon the vesting of restricted stock units over a stated period.

The remarks field is optional and is absent when the filer added no comments. You can also search within it as free text to find notices whose remarks mention a particular topic.

Use the /form-144 endpoint and filter on the issuer CIK (issuerInfo.issuerCik) to isolate one company, then sort by the filing timestamp (filedAt) to order the notices chronologically. This produces the company's Form 144 filings in time sequence.

To measure the trend, read the aggregate market value of each planned sale (securitiesInformation.aggregateMarketValue) and group the values by period—for example by month or quarter of filedAt. The /form-144 endpoint returns the underlying records; the aggregation is performed after the responses are collected, paging through results with the from and size parameters when there are many filings.

Use the /form-144 endpoint with the from and size pagination parameters. The size parameter sets how many filings come back in one response, with a maximum of 50 and a default of 50. The from parameter sets the starting offset into the result set, defaulting to 0.

To walk through a large result set, keep size at 50 and advance from by 50 on each successive request—0, then 50, then 100, and so on. The from offset can go up to 10000, so pagination reaches at most 10,000 filings for a single query. Keep the sort order stable across requests, such as the default sort by filedAt descending, so pages do not overlap or skip records.

Use the /form-144 endpoint and query for the companies you want to compare—for example by their issuer CIKs (issuerInfo.issuerCik) or tickers (issuerInfo.issuerTicker). For each company, read the aggregate market value of the planned sales (securitiesInformation.aggregateMarketValue) from the returned filings.

The /form-144 endpoint does not aggregate across companies; collect the filings per issuer, then sum aggregateMarketValue for each company after the responses are returned to see which companies show the largest planned insider selling. Page through results with the from and size parameters when a company has many notices.

Use the /form-144 endpoint and filter on address fields that carry a non-U.S. state or country code. The seller's location on prior sales is recorded in the prior-sales array (securitiesSoldInPast3Months.sellerDetails.address.stateOrCountry), and the broker handling the sale has its own location (securitiesInformation.brokerOrMarketMakerDetails.address.stateOrCountry), which can sit outside the United States—for example a Grand Cayman address.

The reporting person itself appears as an entry in the entities array (entities.companyName), commonly suffixed with (Reporting), which is where trusts and individual filers are identified. Combine the non-U.S. address codes with the reporting entity name to surface notices tied to foreign or trust-based holders.