---
title: "Get the sequence's playbook"
method: GET
path: "/v3/sequences/ai-sdr/{sequence_id}/playbook"
tags: ["AI SDR Sequences"]
---

# Get the sequence's playbook

`GET /v3/sequences/ai-sdr/{sequence_id}/playbook`

<Warning>
  **Coming soon.** This endpoint will be available by early July 2026.
</Warning>

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

Returns the playbook attached to the sequence. Each sequence is attached to at most one playbook.

Requires the AI SDR feature on the caller's team.

## Path parameters

- `sequence_id` integer, required

## Response `200`

Playbook attached to the sequence

- object — Compact representation of the playbook attached to a sequence.
  - `id` string — Composite playbook id (`{prefix}-{numericId}`) where the prefix encodes the playbook scope: `g` for global, `o` for organization, `t` for team.
  - `name` string — Display name of the playbook
  - `type` 'global' | 'organization' | 'team' — Identifies the visibility scope of a playbook. - `global` — Reply-curated, read-only across all teams. - `organization` — visible to every team in the caller's organization. - `team` — visible to the caller's team only. `global` playbooks are never created or modified via the API; only `organization` and `team` are accepted on create.

## Other responses

- `400` — Sequence exists but is not an AI SDR sequence.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — AI SDR feature is not available for the caller's team, or the caller does not have access to this sequence.
- `404` — Sequence not found, or no playbook is attached to the sequence.
- `502` — Upstream AI SDR service failure.

---

[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/versions/1c3d32eaf95e/schema)