---
title: "Search short interest"
method: GET
path: "/api/v1/short-interest/search"
tags: ["Finance"]
---

# Search short interest

`GET /api/v1/short-interest/search`

Search for a stock in FINRA short interest data by symbol.

## Query parameters

- `q` string, required — Stock symbol (e.g. NVDA, AAPL, GME)
- `limit` integer — Max results

## Response `200`

FINRA short interest records for stocks matching the symbol query.

- EnvelopeShortInterestSearchData
  - `data` ShortInterestSearchData, required
    - `query` string, required — Search query that produced these results.
    - `count` integer, required — Number of items in this result set.
    - `results` ShortInterestResult[], required — Array of result records.
      - `symbol` string, required — Security ticker symbol.
      - `name` string, required — Entity or record name.
      - `latest_short` integer, required
      - `settlement_date` string, required
      - `market` string, required — Market identifier.
    - `recency` HistoryRecency — Whether these rows are proven to be the most recent. The upstream archive answers oldest-first and stops at its own page size, so "the latest N" has to be established rather than asked for. It is established by covering a date window whole. For a symbol producing more rows than a page in the narrowest window tried, that cannot be done, and this block says so rather than letting a full page of older rows pass for recent history. Absent means the rows ARE proven to be the most recent, which is the ordinary case.
      - `proven_most_recent` boolean, required — False when the window could not be covered whole; the block is absent otherwise.
      - `reason` string, nullable — Which obstacle stopped the search, because each calls for a different action. `density` - the symbol reports more rows in a day than the archive returns at once, so a smaller request cannot help. `reach` - no window within the searched span could be read whole, which naming an explicit date range answers. `unreadable` - the upstream stopped answering partway through, which is transient and the same request again is the remedy.
      - `note` string, required — What that means for the caller, and how to close the window.
      - `qualifies` string[] — Which parts of this response the block applies to. The response keeps its ordinary shape when recency is unproven - fields do not appear and disappear with upstream conditions - so this names the affirmative claims that are not proven rather than leaving a client to guess which ones the note covers.
    - `searched_from` string, nullable — The earliest date this search considers - the lower bound of the question, not a claim about what was covered. Always present, because a count means nothing without the period it was counted over, and a count of zero here says nothing about earlier filings. Whether the search actually reached this date is a separate statement: see `recency`, which is present exactly when it did not.
    - `note` string, nullable — Present only when nothing was found: what the empty result does and does not establish.
  - `meta` SugraMeta, required — Metadata attached to every /api/v1/* response envelope.
    - `endpoint` string, required — Requested endpoint path.
    - `data_time` string, required — ISO 8601 UTC timestamp of the source data, not of the request.
    - `response_time` string, required — ISO 8601 UTC timestamp when this response was produced.
    - `provider` string, required — API name and version.
    - `source` string, nullable — Identifier of the primary upstream source used for this response.
    - `attribution` string, nullable — Human-readable attribution mandated by an upstream source (e.g. a securities regulator or self-regulatory organization). Present only on responses whose source requires the owner and source to be clearly identified. Do not remove or alter it when using the response.
    - `fallback_used` boolean, nullable — True when the primary source failed and a fallback produced the data.
    - `fallback_chain` string[], nullable — Ordered list of sources attempted, in the order they were tried.
    - `cached` boolean, nullable — True when this response was served from the internal cache.
    - `stale` boolean, nullable — True when the cached response was returned after the upstream rate-limited or errored. Clients can use this to detect degraded data.

## Other responses

- `401` — Missing or invalid `x-api-key` header. JSON body with a stable `code` distinguishing `missing_api_key` (no header sent) from `invalid_api_key` (header sent, key not accepted); any other 401 source carries the generic `unauthorized` with its detail as `reason`. Plus `hint`. `plan` is always null on 401 - an unauthenticated request has no plan; quota exhaustion is 429, not 401.
- `422` — Validation Error
- `429` — Daily rate limit exceeded. Check `X-RateLimit-Reset` for the next window.
- `503` — Upstream source is temporarily unavailable. Retry after a short delay.

---

[API](https://skmtc.net/sugra/apis/sugra-api.md) · [All operations](https://skmtc.net/sugra/apis/sugra-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sugra/sugra-api/revisions/914af3d38c7c/schema)