> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linkedcamp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Edit copy on existing steps

> **Destructive.** It sends, publishes, launches or deletes. Get a person to confirm before calling it.

Patch fields on already-materialised sequence steps — the surgical way to fix a typo or swap copy on a campaign that is ALREADY RUNNING (ACTIVE or PAUSED), without re-saving the whole graph and re-evaluating every lead. Leads keep their position and their scheduled actions. Pass the step `_id` from `sequence_list` FOR THIS CAMPAIGN, plus only the fields to change — anything omitted is left alone. An id from another campaign is refused. Copy fields: `message`, `subject`, `note` (the connection-request note), `shortNote`, and the A/B variants `bMessage`, `bSubject`, `bNote`, `bShortNote`. Read the step back from `sequence_list` first to see which of those it actually has — an EMAIL step has `subject`, a CONNECT step has `note`, and only a step with `abTestingEnabled` uses the `b*` pair. TWO EDITS ARE NOT SURGICAL AND ARE EASY TO MAKE BY ACCIDENT. Sending `days` or `calendarType` RESCHEDULES every pending activity on that step — each waiting lead is pushed to that many days from now, which moves real send times; neither field is returned by `sequence_list`, so do not pass them unless the user asked to change the wait. And `connectWithoutMessage: true` silently CLEARS that step's `note`, so the connection request goes out with no text. To add, remove or reorder steps, rewrite the sequence with `flow_set`. Do NOT use this on a DRAFTED campaign: launching rebuilds every step from the saved flow graph, which this endpoint does not touch, so the edit is silently reverted to the original copy the moment the campaign launches. Check `status` with `campaign_get` first. To change a draft's copy, call `flow_set` again with the corrected steps.



## OpenAPI

````yaml /api-v2/openapi.json post /sequence_update
openapi: 3.1.0
info:
  title: LinkedCamp API
  version: 2.0.0
  description: >-
    Version 2 of the LinkedCamp API. Every endpoint is a POST to `/{endpoint}`
    with its arguments as a JSON object, and returns JSON.
servers:
  - url: https://api.linkedcamp.com/v2
security:
  - ApiKey: []
  - Bearer: []
tags:
  - name: Account
  - name: Notifications
  - name: Reference
  - name: Campaigns
  - name: Campaign audience
  - name: Sequences
  - name: Blocked dates
  - name: Leads
  - name: Lead notes
  - name: Activities
  - name: Tags
  - name: Blacklist
  - name: Conversations
  - name: Messages
  - name: Saved replies
  - name: Templates
  - name: Merge fields
  - name: Personalised images
  - name: LinkedIn accounts
  - name: Email accounts
  - name: AI agents
  - name: Knowledge base
  - name: Personas
  - name: Analytics
  - name: Posts
  - name: Posting schedule
  - name: Tasks
  - name: Appointments
  - name: Reminders
  - name: Automations
paths:
  /sequence_update:
    post:
      tags:
        - Sequences
      summary: Edit copy on existing steps
      description: >-
        **Destructive.** It sends, publishes, launches or deletes. Get a person
        to confirm before calling it.


        Patch fields on already-materialised sequence steps — the surgical way
        to fix a typo or swap copy on a campaign that is ALREADY RUNNING (ACTIVE
        or PAUSED), without re-saving the whole graph and re-evaluating every
        lead. Leads keep their position and their scheduled actions. Pass the
        step `_id` from `sequence_list` FOR THIS CAMPAIGN, plus only the fields
        to change — anything omitted is left alone. An id from another campaign
        is refused. Copy fields: `message`, `subject`, `note` (the
        connection-request note), `shortNote`, and the A/B variants `bMessage`,
        `bSubject`, `bNote`, `bShortNote`. Read the step back from
        `sequence_list` first to see which of those it actually has — an EMAIL
        step has `subject`, a CONNECT step has `note`, and only a step with
        `abTestingEnabled` uses the `b*` pair. TWO EDITS ARE NOT SURGICAL AND
        ARE EASY TO MAKE BY ACCIDENT. Sending `days` or `calendarType`
        RESCHEDULES every pending activity on that step — each waiting lead is
        pushed to that many days from now, which moves real send times; neither
        field is returned by `sequence_list`, so do not pass them unless the
        user asked to change the wait. And `connectWithoutMessage: true`
        silently CLEARS that step's `note`, so the connection request goes out
        with no text. To add, remove or reorder steps, rewrite the sequence with
        `flow_set`. Do NOT use this on a DRAFTED campaign: launching rebuilds
        every step from the saved flow graph, which this endpoint does not
        touch, so the edit is silently reverted to the original copy the moment
        the campaign launches. Check `status` with `campaign_get` first. To
        change a draft's copy, call `flow_set` again with the corrected steps.
      operationId: sequence_update
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                campaignId:
                  type: string
                  description: Campaign id, from `campaign_list` or `campaign_create`.
                sequences:
                  type: array
                  items:
                    type: object
                    properties:
                      _id:
                        type: string
                        description: >-
                          Sequence step id, from `sequence_list` for THIS
                          campaign. An id belonging to another campaign is
                          refused.
                    required:
                      - _id
                    additionalProperties: {}
                    description: >-
                      The step id plus only the fields to overwrite, e.g. {
                      "_id": "…", "message": "new copy" } or { "_id": "…",
                      "subject": "…", "bSubject": "…" } for both halves of an
                      A/B step. Omitted fields keep their current value. Do not
                      include `days` or `calendarType` unless the user asked to
                      change the wait — they reschedule every pending activity
                      on the step.
                  minItems: 1
                  description: The step patches to apply.
              required:
                - campaignId
                - sequences
              additionalProperties: false
      responses:
        '200':
          description: >-
            The result, as JSON. Writes answer `{ "ok": true, "message": ...,
            "data": ... }`.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: >-
            The body is not valid JSON, an argument is invalid, or the request
            was refused.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: No API key, or the key was rejected.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            Your plan, permissions or access tier don't include this, or a
            record belongs to another account.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: A record named in the arguments does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: >-
            The request was valid but the operation was refused, such as
            launching a campaign that is not ready.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '502':
          description: The service failed or could not be reached. Reads are safe to retry.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '504':
          description: >-
            The operation timed out. A write may still complete; read it back
            before retrying.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              enum:
                - UNAUTHENTICATED
                - FORBIDDEN
                - PLAN_REQUIRED
                - VALIDATION
                - INVALID_JSON
                - NOT_FOUND
                - METHOD_NOT_ALLOWED
                - UPSTREAM
                - TOOL_ERROR
            message:
              type: string
            hint:
              type: string
              description: What to do about it, when there is something to do.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: Your LinkedCamp API key.
    Bearer:
      type: http
      scheme: bearer
      description: Your LinkedCamp API key as a bearer token.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.