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

# Get a contact's statuses

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

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

Returns the contact's current global flags (`isOptedOut`, `callStatus`, `meetingStatus`) plus per-sequence status (`statusInSequence`) and email disposition (`isReplied`, `isBounced`) for each sequence the contact is enrolled in.

## Path parameters

- `id` integer, required

## Response `200`

Contact statuses retrieved successfully

- object
  - `contactId` integer, required — Contact ID
  - `isOptedOut` boolean, required — Whether the contact has opted out of all communications
  - `callStatus` 'none' | 'toCall' | 'called', required — Contact-level call status. Set via `PATCH /v3/contacts/{id}` (`callStatus` field). Pass `none` to clear.
  - `meetingStatus` 'none' | 'meetingBooked', required — Contact-level meeting status. Set via `PATCH /v3/contacts/{id}` (`meetingStatus` field). Pass `none` to clear.
  - `sequences` object[], required — Per-sequence status for every sequence the contact is enrolled in. Empty when the contact is not in any sequence.
    - `sequenceId` integer, required
    - `sequenceName` string, required
    - `statusInSequence` 'active' | 'paused' | 'inactive' | 'invalidEmail' | 'outOfOffice' | 'finished' | 'contacted' | 'opened' | 'clicked' | 'autoReplied' | 'bounced' | 'replied', required — All in-sequence status values that can appear in the `statusInSequence` field of `GET /v3/contacts/{id}/statuses` (per-sequence entries). Includes derived values (e.g. `inactive`, `contacted`, `opened`, `clicked`, `autoReplied`) that the API does not allow you to set directly — only the values in `contact-status.enum.yaml` are writable.
    - `emailDisposition` object, required
      - `isReplied` boolean, required
      - `isBounced` boolean, required

## 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.
- `404` — Contact not found

---

[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)