# Sequences API > The sequences resource lets external systems prepare, migrate, or synchronize time-based email series. This guide explains how to plan sequence definitions, when to update or delete sequences, and what to check before migrated journeys reach real subscribers. - Human page: https://mailrith.com/developers/sequences - Markdown page: https://mailrith.com/developers/sequences.md - Category: API Resources - Reading time: 6 min read - Last updated: 2026-06-13 - Related keywords: Sequences API, Sequences API developer docs, API Resources, API Resources developer docs, Mailrith developer docs, Mailrith public API, Manage Timed Email Series, Endpoint Overview, Migration Notes, Email Templates API, Automations API, API Reference ## AI Agent Notes - Use this page as implementation guidance, then validate exact endpoint fields against the OpenAPI document. - Keep API keys server-side and workspace-scoped unless a guide explicitly says otherwise. - Do not invent privacy, consent, or lawful-basis evidence. Send only fields that appear in the OpenAPI schema for the endpoint you are using. ## What this guide covers Manage timed email series for onboarding, nurture, migration, and lifecycle workflows. ## Manage Timed Email Series Sequences are timed email series. Use them for onboarding, nurture campaigns, customer education, follow-up flows, and other journeys where subscribers receive multiple emails over time. Use the sequences API for migration, external content review, internal campaign tooling, or setup scripts that prepare a workspace before users run campaigns. Sequence definitions can affect subscriber journeys for days or weeks. Use clear names, descriptions, steps, and timing so the people who review or operate the sequences in Mailrith can understand them. 1. List existing sequences before creating new ones so you do not import duplicates. 2. Create the sequence definition with a clear name and purpose. 3. Add or update email steps in the order that subscribers should receive them. Then ask a Mailrith user to review the step order in the sequence editor. 4. Confirm that delays, sending windows, and filters match the source system or planned journey. 5. Ask a user to test every step in [Sequences](https://mailrith.com/docs/sequences.md) before enrolling real subscribers. 6. Keep migration notes that map the source-system sequence to the Mailrith sequence ID. - List sequences when you audit or sync existing lifecycle content. - Create sequences when you import journeys from another platform. - Update sequences when an external source of truth changes content or timing. - Delete sequences only after you confirm that no active workflow still depends on the sequence definition. ## Endpoint Overview `GET /v1/sequences` lists sequence definitions. Item endpoints let integrations inspect, update, or delete one sequence. `POST /v1/sequences` creates a sequence definition. The payload describes the series, including email steps, timing, and content-related settings supported by the OpenAPI schema. Use the generated reference for exact field names. Do not copy internal app state from the browser, because the public API is the stable contract. Related OpenAPI operation groups: - Sequences ## Migration Notes When you migrate from another platform, first recreate the sequence structure as drafts or inactive definitions if your workflow supports review before launch. Then compare the Mailrith version with the source-system version before activating the sequence for real subscribers. Pay special attention to timing. A one-day delay, send window, or missing stop condition can change the subscriber experience even when the email copy is correct. - Map source emails to Mailrith sequence steps in order. - Confirm that delay values and time units are correct. - Check personalization variables in every email body. - In Mailrith, open the sequence, click each step's `Email Settings`, and send test emails before enrolling real subscribers. - Document which source sequence created the Mailrith sequence so future cleanup is easier. ## Related Guides - [Email Templates API](https://mailrith.com/developers/email-templates.md): The email templates resource supports migrations, governance, and external template sync. This guide explains when to use templates, how to preserve structured editor content, and how to keep template names and descriptions useful for workspace users. - [Automations API](https://mailrith.com/developers/automations.md): The automations resource exposes Mailrith workflow definitions for tools that create or synchronize automations outside the app. This guide explains what automations can affect, how to use the public schema, and what to review before you trust a generated workflow. - [API Reference](https://mailrith.com/developers/api-reference.md): The full API reference is generated from the same public contract used by the API worker and SDK tooling. Use the API reference to find exact paths, methods, parameters, request schemas, response schemas, operation IDs, and the downloadable OpenAPI document.