---
title: "List exceptions"
method: GET
path: "/v1/exceptions"
tags: ["Exception"]
---

# List exceptions

`GET /v1/exceptions`

Use this endpoint to retrieve all exceptions. You can filter the results by status, severity, assigned user, external system, and date range. The response uses cursor-based pagination.

## Query parameters

- `status` 'OPEN' | 'ASSIGNED' | 'PENDING_RESOLUTION' | 'RESOLVED'
- `severity` 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL'
- `assigned_to` string
- `external_system` 'JIRA' | 'SERVICENOW' | 'WEBHOOK'
- `date_from` string
- `date_to` string
- `cursor` string
- `limit` integer
- `sort_by` 'id' | 'created_at' | 'updated_at' | 'severity' | 'status'
- `sort_order` 'asc' | 'desc'

## Headers

- `X-Request-Id` string

## Response `200`

Indicates that the request was successful and the response contains the expected data.

- ListExceptionsResponse — Paginated list of exceptions
  - `hasMore` boolean
  - `items` ExceptionResponse[] — List of exceptions
    - `assignedTo` string — User the exception is assigned to
    - `createdAt` string — Creation timestamp in RFC3339 format
    - `dueAt` string — Due date for resolution in RFC3339 format
    - `externalIssueId` string — External issue ID in the external system
    - `externalSystem` string — External system where exception was dispatched
    - `id` string — Unique identifier for the exception
    - `reason` string — Reason the exception was raised
    - `resolutionNotes` string — Resolution notes when resolved
    - `resolutionReason` string — Reason for the resolution
    - `resolutionType` 'FORCE_MATCH' | 'ADJUST_ENTRY' — Type of resolution applied
    - `severity` 'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL' — Severity level
    - `status` 'OPEN' | 'ASSIGNED' | 'PENDING_RESOLUTION' | 'RESOLVED' — Current status
    - `transactionId` string — Transaction ID this exception is for
    - `updatedAt` string — Last update timestamp in RFC3339 format
  - `limit` integer
  - `nextCursor` string
  - `prevCursor` string

## Other responses

- `400` — The request contains invalid parameters or payload.
- `401` — The request lacks valid authentication credentials.
- `403` — You do not have permission to access this resource.
- `500` — An unexpected error occurred on the server.

---

[API](https://skmtc.net/lerian/apis/identity-plugin.md) · [All operations](https://skmtc.net/lerian/apis/identity-plugin/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lerian/identity-plugin/versions/25daba385532/schema)