---
title: "List sequences in a folder"
method: GET
path: "/v3/sequence-folders/{id}/sequences"
tags: ["Sequence Folders"]
---

# List sequences in a folder

`GET /v3/sequence-folders/{id}/sequences`

<small>_Requires the `sequences:read` scope (or a broader one that includes it)._</small>

Returns a paginated list of sequences in a folder

## Path parameters

- `id` string, uuid, required

## Query parameters

- `top` integer
- `skip` integer
- `sort_by` string
- `sort_direction` 'asc' | 'desc'

## Response `200`

List of sequences in folder retrieved successfully

- object — Response model for listing sequences with pagination
  - `items` object[] — Array of sequence items
    - `id` integer — Unique identifier for the sequence
    - `ownerUserId` integer — Identifier of the user who owns the sequence
    - `name` string — Name of the sequence
    - `created` string, date-time — Sequence creation timestamp with timezone offset
    - `status` 'new' | 'active' | 'paused' — Current status of the sequence
    - `isArchived` boolean — Indicates if the sequence is archived
    - `health` 'healthy' | 'stalled' | 'degraded' | 'blocked' — Overall health status of the sequence. Indicates whether the sequence can operate normally or has issues that need attention. - `healthy` — Sequence is functioning normally with no issues - `stalled` — Sequence has stalled and is not progressing - `degraded` — Sequence is running but with reduced effectiveness - `blocked` — Sequence cannot proceed due to critical issues
  - `hasMore` boolean — Indicates if there are more items to fetch

## Other responses

- `400` — Invalid pagination or sort
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to view sequences in this folder
- `404` — Sequence folder not found
- `429` — Too Many Requests

---

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