# Add leads to a subsequence campaign

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /lead/add-lead-in-subseq:
    post:
      summary: Add leads to a subsequence campaign
      deprecated: false
      description: >-
        Add existing leads from a parent campaign to a subsequence campaign.
        This allows you to move leads that have completed one campaign sequence
        into a follow-up sequence.
      operationId: Lead_lead/add-leads-to-a-subsequence-campaign
      tags:
        - Lead
        - Lead
      parameters:
        - name: X-API-Key
          in: header
          description: Your PlusVibe.ai account's API Key
          required: false
          example: ''
          schema:
            type: string
            description: Your PlusVibe.ai account's API Key
            default: ''
            examples:
              - your-api-key
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                workspace_id:
                  type: string
                  description: ID of the workspace where the campaigns exist
                subseq_id:
                  type: string
                  description: ID of the subsequence campaign to add leads to
                parent_lead_ids:
                  type: array
                  items:
                    type: string
                  description: >-
                    Array of lead IDs from the parent campaign. These leads must
                    exist in the parent campaign associated with the
                    subsequence.
              required:
                - workspace_id
                - subseq_id
                - parent_lead_ids
              x-apidog-orders:
                - workspace_id
                - subseq_id
                - parent_lead_ids
            example:
              workspace_id: 65099a0dd96fae8ab61130c0
              subseq_id: 67b0c400da2ea90b8d13ba83
              parent_lead_ids:
                - 6794fe5b3a8714787fdaf26e
      responses:
        '200':
          description: Successfully added leads to subsequence
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    description: Status of the operation
                    examples:
                      - success
                  inserted:
                    type: integer
                    description: Number of leads successfully added to the subsequence
                    examples:
                      - 1
                x-apidog-orders:
                  - status
                  - inserted
          headers: {}
          x-apidog-name: OK
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    description: ''
                    examples:
                      - error
                  message:
                    type: string
                    description: ''
                    examples:
                      - Invalid lead IDs or subsequence ID
                x-apidog-orders:
                  - status
                  - message
          headers: {}
          x-apidog-name: Bad Request
      security:
        - ApiKeyAuth: []
          x-apidog:
            schemeGroups:
              - id: uS5KiuC4wfZHK42AzOfA_
                schemeIds:
                  - ApiKeyAuth
            required: true
            use:
              id: uS5KiuC4wfZHK42AzOfA_
            scopes:
              uS5KiuC4wfZHK42AzOfA_:
                ApiKeyAuth: []
      x-apidog-folder: Lead
      x-apidog-status: released
      x-run-in-apidog: https://app.apidog.com/web/project/929054/apis/api-17238008-run
components:
  schemas: {}
  securitySchemes:
    ApiKeyAuth:
      type: apikey
      in: header
      name: x-api-key
      description: |
        API key issued in the PlusVibe dashboard. The server reads it
        from the `x-api-key` header and injects it into the request as
        the `api_key` query parameter, which is why you will see
        `api_key` referenced in validation errors.
    apiKey:
      type: apikey
      in: body
      name: api_key
      description: API key passed in request body
servers:
  - url: https://api.plusvibe.ai/api/v1
    description: Prod Env
security:
  - ApiKeyAuth: []
    x-apidog:
      schemeGroups:
        - id: uS5KiuC4wfZHK42AzOfA_
          schemeIds:
            - ApiKeyAuth
      required: true
      use:
        id: uS5KiuC4wfZHK42AzOfA_
      scopes:
        uS5KiuC4wfZHK42AzOfA_:
          ApiKeyAuth: []

```