---
title: "Get a Sequence Template"
method: GET
path: "/v1/sequence-templates/{sequence_template_id}"
tags: ["Sequence Templates"]
---

# Get a Sequence Template

`GET /v1/sequence-templates/{sequence_template_id}`

Gets a single sequence template by its `sequence_template_id`. The detail response includes the template's ordered list of steps.

## Path parameters

- `sequence_template_id` string, uuid, required

## Response `200`

Successful Response

- PublicItemResponseSequenceTemplateDetailResponse
  - `data` SequenceTemplateDetailResponse, required — Sequence template with its ordered list of steps and transitions.
    - `id` string, required — Unique identifier for the sequence template
    - `name` string, required — Name of the sequence template
    - `description` string, nullable — Description of the sequence template
    - `status` 'ACTIVE' | 'INACTIVE' | 'DRAFT' | 'ARCHIVED', required
    - `owner_id` string, nullable — ID of the user who owns the sequence template
    - `is_default` boolean — Whether this template is the default for the organization
    - `archived_at` string, date-time, nullable — Date and time the sequence template was archived
    - `created_at` string, date-time, nullable — Date and time the sequence template was created
    - `updated_at` string, date-time, nullable — Date and time the sequence template was last updated
    - `steps` SequenceTemplateStepResponse[] — Ordered list of steps in the template
      - `id` string, required — Unique identifier for the step
      - `index` integer, nullable — Position of the step within the template (1-based)
      - `title` string, nullable — Display title of the step
      - `day` integer, nullable — Day offset from the start of the sequence
      - `hour` integer, nullable — Hour of day the step is scheduled for
      - `type` 'generic' | 'auto_email' | 'manual_email' | 'auto_linkedin_connection' | 'manual_linkedin_connection' | 'auto_linkedin_message' | 'manual_linkedin_message' | 'auto_linkedin_inmail' | 'manual_linkedin_inmail' | 'auto_phone' | 'manual_phone' | 'internal_email' | 'gifting_via_email' | 'gifting_via_address' | 'complete_sequence', required
      - `subject` string, nullable — Subject line (email and gifting steps)
      - `message` string, nullable — Message body for the step
      - `gift_id` string, nullable — ID of the gift attached to a gifting step
    - `transitions` SequenceTemplateTransitionResponse[] — Transitions between steps (ordering and branching rules)
      - `from_step_index` integer, required — Index of the source step within the template
      - `to_step_index` integer, required — Index of the destination step within the template
      - `transition_type` 'PREVIOUS_STEP_COMPLETES' | 'PREVIOUS_STEP_RUNS' | 'GIFT_DELIVERED' | 'PREVIOUS_STEP_SCHEDULED' | 'LINKEDIN_REQUEST_ACCEPTED' | 'LINKEDIN_REQUEST_NOT_ACCEPTED' | 'GIFT_ACCEPTED' | 'GIFT_NOT_ACCEPTED', required
      - `pre_check_time_unit` string — Time unit for `pre_check_delay`. One of `seconds`, `minutes`, `hours`, `days`, or `business_days`.
      - `pre_check_delay` integer, nullable — A grace window before this transition's condition starts being evaluated, measured from when the source step completed (in `pre_check_time_unit`). Use it when the condition could be satisfied immediately but you want to wait first — e.g. after an email is sent, hold off 2 business days before checking for a reply, giving the prospect time to respond. `null` or `0` evaluates as soon as the source step completes.
      - `post_check_time_unit` string — Time unit for `post_check_delay`. One of `seconds`, `minutes`, `hours`, `days`, or `business_days`.
      - `post_check_delay` integer, nullable — A pacing delay after this transition's condition has passed, before the destination step is scheduled (in `post_check_time_unit`). Use it to avoid an instantaneous, robotic-feeling response to a prospect-driven event — e.g. wait a business day after a LinkedIn connection is accepted before pitching, or after a gift is delivered before the thank-you. `null` or `0` schedules the next step immediately.
      - `require_all` boolean — Whether all conditions must be met (vs. any of them)
    - `blocks` object — Content blocks referenced anywhere in this template, keyed by block id. A step's subject/message may contain [[block:<uuid>]] markers; each <uuid> appears as a key in this dict.
  - `meta` ResponseMeta
    - `timestamp` string, date-time — Server timestamp of the response

## Other responses

- `404` — Not Found
- `4XX` — Client error

---

[API](https://skmtc.dev/monaco/apis/monaco-public-api.md) · [All operations](https://skmtc.dev/monaco/apis/monaco-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/monaco/monaco-public-api/revisions/ec4d9b2b035b/schema)