---
title: "Get sequences for a contact"
method: GET
path: "/v3/contacts/{id}/sequences"
tags: ["Contacts"]
---

# Get sequences for a contact

`GET /v3/contacts/{id}/sequences`

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

Use this endpoint when you need to see which sequences a contact is enrolled in, together with each sequence's name, the contact's status in it, the current step, and when they were added.

## Path parameters

- `id` integer, required

## Response `200`

Contact sequences retrieved successfully

- object[]
  - `sequenceId` integer
  - `sequenceName` string
  - `statusInSequence` 'active' | 'paused' | 'finished' | 'outOfOffice' — Workflow status of the contact within this sequence
  - `currentStep` object, nullable — Position of the contact in the sequence's step graph (`stepId` + `displayName`). `null` for memberships outside of an active step.
    - `stepId` integer, nullable — Database id of the current step. `null` if the contact has no current step (finished or archived).
    - `displayName` string, nullable — Human-readable label for the step. `"Finished"` when the contact is finished.
  - `addingDate` string, date-time, nullable
  - `emailAccountId` integer, nullable
  - `linkedInAccountId` integer, nullable

## Other responses

- `400` — Route-parameter validation failure (e.g. non-positive `id`) or a business rule rejection.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to view this contact
- `404` — Contact 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)