---
title: "List"
method: POST
path: "/v1/verdict_reasons/list"
tags: ["Fraud"]
---

# List

`POST /v1/verdict_reasons/list`

## Request

- Base URL: `https://telemetry.stytch.com`
- URL: `https://telemetry.stytch.com/v1/verdict_reasons/list`
- Auth: HTTP basic

Get the list of verdict reasons returned by the Stytch Device Fingerprinting product along with their default actions and any overrides you may have defined. This is not an exhaustive list of verdict reasons, but it contains all verdict reasons that you may set an override on.

For a full list of possible verdict reasons, see [Warning Flags (Verdict Reasons)](https://stytch.com/docs/docs/fraud/guides/device-fingerprinting/reference/warning-flags-verdict-reasons).

## Request body

- ApiFraudV1FraudVerdictReasonsListRequest: Request type
  - `overrides_only` boolean: Whether to return only verdict reasons that have overrides set. Defaults to false.

## Response `200`

Successful response

- ApiFraudV1FraudVerdictReasonsListResponse
  - `request_id` string, required: Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
  - `verdict_reason_actions` ApiFraudV1VerdictReasonAction[], required: Information about verdict reasons and any overrides that were set on them.
    - `verdict_reason` string, required: The verdict reason.
    - `default_action` 'ALLOW' | 'CHALLENGE' | 'BLOCK', required
    - `override_action` 'ALLOW' | 'CHALLENGE' | 'BLOCK'
    - `override_created_at` string: The time when the override was created, if one exists. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. `2021-12-29T12:33:09Z`.
    - `override_description` string: A description of the override, if one exists.
  - `status_code` integer, required: The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `429`: Too Many Requests
- `500`: Internal server error

## Changes

- **2026-03-07** `110f26a94e5b`: 1 info
  - endpoint added
- **2026-03-06** `9cab20b8eca7`: 1 breaking
  - api path removed without deprecation
- **2025-09-17** `8270cf3a3d4c`: 3 info
  - added the media type `application/json` for the response with the status `401`
  - added the media type `application/json` for the response with the status `500`
  - added the non-success response with the status `429`
- **2025-09-17** `864b9f438ac0`: 2 breaking
  - the `overrides_only` request property type changed from `string` to `boolean`
  - the `status_code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `200`

[Operation history](https://skmtc.dev/stytch/apis/stytch-api/changes/v1/verdict_reasons/list/post.md)

---

[API](https://skmtc.dev/stytch/apis/stytch-api.md) - [All operations](https://skmtc.dev/stytch/apis/stytch-api/llms.txt) - [OpenAPI document](https://skmtc.dev/stytch/apis/stytch-api/revisions/6d1ff7474803?raw)