---
title: "Changes to Predefined screener (gainers, losers, most active, etc.)"
method: GET
path: "/api/v2/market/screener/{scr_id}"
---

# Changes to Predefined screener (gainers, losers, most active, etc.)

`GET /api/v2/market/screener/{scr_id}`

> Every recorded change to this operation, newest first.
> 45 revisions in range; 1 not diffed.

## Timeline

Changed in 6 of 45 revisions.

- **2026-10-18** `62345201d043`: 1 breaking, 28 info
- **2026-09-13** `d2472ec2cf81`: 3 breaking, 5 warning, 3 info
- **2026-09-09** `4f8853a61440`: 1 info
- **2026-09-01** `328d061c12ca`: 3 info
- **2026-08-24** `64715a22734d`: 7 info
- **2026-08-08** `4c4530760ba1`: 12 info

## Changes

- **2026-10-18** `62345201d043`: 1 breaking, 28 info
  - the `path` request parameter `scr_id` was restricted to a list of enum values
  - added the new enum value `ALL_CRYPTOCURRENCIES_US` to the `path` request parameter `scr_id`
  - added the new enum value `BEST_HIST_PERFORMANCE_ETFS` to the `path` request parameter `scr_id`
  - added the new enum value `BEST_HIST_PERFORMANCE_MUTUAL_FUNDS` to the `path` request parameter `scr_id`
  - added the new enum value `DAY_GAINERS_ETFS` to the `path` request parameter `scr_id`
  - added the new enum value `DAY_GAINERS_MUTUAL_FUNDS` to the `path` request parameter `scr_id`
  - added the new enum value `DAY_GAINERS_OPTIONS` to the `path` request parameter `scr_id`
  - added the new enum value `DAY_LOSERS_ETFS` to the `path` request parameter `scr_id`
  - added the new enum value `DAY_LOSERS_MUTUAL_FUNDS` to the `path` request parameter `scr_id`
  - added the new enum value `DAY_LOSERS_OPTIONS` to the `path` request parameter `scr_id`
  - added the new enum value `HIGHEST_VALUATION_PRIVATE_COMPANY` to the `path` request parameter `scr_id`
  - added the new enum value `MOST_ACTIVES` to the `path` request parameter `scr_id`
  - added the new enum value `MOST_ACTIVES_ETFS` to the `path` request parameter `scr_id`
  - added the new enum value `MOST_ACTIVES_OPTIONS` to the `path` request parameter `scr_id`
  - added the new enum value `TOP_ETFS_US` to the `path` request parameter `scr_id`
  - added the new enum value `TOP_MUTUAL_FUNDS` to the `path` request parameter `scr_id`
  - added the new enum value `TOP_OPTIONS_IMPLIED_VOLATALITY` to the `path` request parameter `scr_id`
  - added the new enum value `TOP_OPTIONS_OPEN_INTEREST` to the `path` request parameter `scr_id`
  - added the new enum value `TOP_PERFORMING_ETFS` to the `path` request parameter `scr_id`
  - added the new enum value `TOP_PERFORMING_MUTUAL_FUNDS` to the `path` request parameter `scr_id`
  - added the new enum value `aggressive_small_caps` to the `path` request parameter `scr_id`
  - added the new enum value `day_gainers` to the `path` request parameter `scr_id`
  - added the new enum value `day_losers` to the `path` request parameter `scr_id`
  - added the new enum value `growth_technology_stocks` to the `path` request parameter `scr_id`
  - added the new enum value `most_active_penny_stocks` to the `path` request parameter `scr_id`
  - added the new enum value `most_shorted_stocks` to the `path` request parameter `scr_id`
  - added the new enum value `recent_52_week_lows` to the `path` request parameter `scr_id`
  - added the new enum value `undervalued_growth_stocks` to the `path` request parameter `scr_id`
  - added the new enum value `undervalued_large_caps` to the `path` request parameter `scr_id`
- **2026-09-13** `d2472ec2cf81`: 3 breaking, 5 warning, 3 info
  - added `#/components/schemas/UpstreamErrorResponse, subschema #2` to the response body `oneOf` list for the response status `503`
  - the response's body type changed from `object` to no type for status `503`
  - removed the required property `error` from the response with the `503` status
  - removed the optional property `code` from the response with the `503` status
  - removed the optional property `detail` from the response with the `503` status
  - removed the optional property `hint` from the response with the `503` status
  - removed the optional property `plan` from the response with the `503` status
  - removed the optional property `reason` from the response with the `503` status
  - added the non-success response with the status `500`
  - added the non-success response with the status `502`
  - added the non-success response with the status `504`
- **2026-09-09** `4f8853a61440`: 1 info
  - added the optional property `meta/stale_since` to the response with the `200` status
- **2026-09-01** `328d061c12ca`: 3 info
  - added the optional property `meta/data_age_days` to the response with the `200` status
  - added the optional property `meta/notes` to the response with the `200` status
  - added the optional property `meta/period` to the response with the `200` status
- **2026-08-24** `64715a22734d`: 7 info
  - added the optional property `data/count` to the response with the `200` status
  - added the optional property `data/description` to the response with the `200` status
  - added the optional property `data/records` to the response with the `200` status
  - added the optional property `data/screener_id` to the response with the `200` status
  - added the optional property `data/start` to the response with the `200` status
  - added the optional property `data/title` to the response with the `200` status
  - added the optional property `data/total` to the response with the `200` status
- **2026-08-08** `4c4530760ba1`: 12 info
  - added the optional property `code` to the response with the `401` status
  - added the optional property `code` to the response with the `429` status
  - added the optional property `code` to the response with the `503` status
  - added the optional property `hint` to the response with the `401` status
  - added the optional property `hint` to the response with the `429` status
  - added the optional property `hint` to the response with the `503` status
  - added the optional property `plan` to the response with the `401` status
  - added the optional property `plan` to the response with the `429` status
  - added the optional property `plan` to the response with the `503` status
  - added the optional property `reason` to the response with the `401` status
  - added the optional property `reason` to the response with the `429` status
  - added the optional property `reason` to the response with the `503` status

---

[Operation](https://skmtc.dev/sugra/apis/sugra-api/docs/api/v2/market/screener/:scr_id/get.md) · [API](https://skmtc.dev/sugra/apis/sugra-api.md) · [Page](https://skmtc.dev/sugra/apis/sugra-api/changes/api/v2/market/screener/:scr_id/get)