> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/forms/144

> Return recent Form 144 notices of proposed insider sales with cursor pagination and date filters

Return recent Form 144 notices of proposed insider sales with cursor pagination and date filters

<Info>
  Audience: application and coding agent.
</Info>

## Coverage and source scope

Use this route to review filed notices of proposed Rule 144 sales by an issuer's affiliates. A notice is not a completed sale, a trade execution record, or a measure of the holder's remaining position; corroborate a later Form 4 or other filing when the workflow needs completed transactions. `date_from` and `date_to` bound filing dates, and `submission_file_limit` can reduce the SEC submission history searched, which can omit older records. Follow `nextCursor` with the same filters. See [filing conventions](/api-conventions) and [insider transaction workflows](/api-reference/insiders).

## Agent mode

Pass `?view=agent` to receive the compact agent shape: 7 citation fields (object, ticker, form, filingDate, accessionNumber, title, filingUrl). Id, entityId, companyName, sourceSurface, legalShareability, and metadata envelopes are dropped. Typical reduction: **\~65%**. See [api conventions → response formats](/api-conventions) for the full `?view=` contract.

## Canonical metadata

* `requestId`
* `traceparent`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "x-api-key: $SECAPI_API_KEY" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/forms/144"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/forms/144 to review filed notices of proposed Rule 144 affiliate sales. Start with a ticker or CIK when known and use `date_from` and `date_to` as filing-date bounds. Preserve the accession number, filing date, filing URL, `hasMore`, `nextCursor`, `requestId`, and `traceparent`; when present, preserve `provenance`, `freshness`, and `materialization` metadata unchanged, but do not assume those fields on response shapes that omit them. A Form 144 is not a completed sale or a holder-position update. Keep the same filters while following `nextCursor`, and note that a lower `submission_file_limit` can omit older SEC matches.
</Prompt>

## Failure posture

* treat non-2xx responses as contract-aware failures, not free-form errors
* preserve `requestId` and `traceparent` in logs and downstream reports
* if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff