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

# List a campaign's drip steps

> Returns the ordered drip-sequence steps configured for a campaign — each step's send delay, channel, message template, optional email subject, and any branching condition. Steps come back sorted by their `order`. Use it to render or pre-fill the drip builder. Read-only; returns 404 when the campaign does not exist.



## OpenAPI

````yaml /openapi.yaml get /api/v1/campaigns/{id}/steps
openapi: 3.1.0
info:
  title: Devotel CPaaS API
  description: Orbit by Devotel — Communications Platform as a Service API
  version: 1.0.0
  contact:
    name: Devotel
    url: https://devotel.io
    email: support@devotel.io
  license:
    name: Proprietary
servers:
  - url: https://api.orbit.devotel.io
    description: Production
security:
  - Bearer: []
  - ApiKey: []
tags:
  - name: Messages
    description: >-
      Send and manage messages across all channels (SMS, WhatsApp, RCS, Email,
      Viber, etc.)
  - name: Fax
    description: >-
      List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers
      (sending flows through the Messaging API)
  - name: Agents
    description: AI agent creation, configuration, and execution
  - name: Voice
    description: Voice calls, IVR, conferencing, and SIP trunking
  - name: OnCall
    description: On-call rotations and escalation policy planning for incident alerting
  - name: Webhooks
    description: Webhook endpoint management and delivery logs
  - name: Numbers
    description: Phone number search, provisioning, and configuration
  - name: Brand Identity
    description: >-
      Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp,
      RCS, branded calling, number KYC)
  - name: Contacts
    description: Contact management, segmentation, and lifecycle tracking
  - name: Campaigns
    description: Marketing campaign orchestration and analytics
  - name: Flows
    description: Automation flow builder and execution engine
  - name: Templates
    description: Message template management and approval workflows
  - name: Settings
    description: Organization, channel, and user preference settings
  - name: Verify
    description: OTP generation and verification across channels
  - name: Push
    description: Push notification delivery via FCM and APNs
  - name: Integrations
    description: Third-party service connections and OAuth management
  - name: CDP
    description: >-
      Customer Data Platform — activation surface (CRM object sync, streaming
      destinations, ad-audience activation)
  - name: Files
    description: >-
      Server-to-server media upload, listing, retrieval, and deletion
      (signed-URL backed)
  - name: Commerce
    description: >-
      Omnichannel conversational-commerce — persistent cart + checkout state
      machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout,
      and AP2-style agent payment mandates.
  - name: Sync
    description: >-
      Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps,
      Lists, and ephemeral Streams, with change events relayed over the
      /api/v1/ws/sync WebSocket gateway
  - name: Risk
    description: >-
      Unified cross-channel Trust & Fraud risk scoring — fuses SMS-pumping,
      URL-reputation, Verify Fraud Guard, and Voice Biometrics signals into one
      composite verdict queryable before a send or a call.
  - name: Orby
    description: >-
      In-dashboard Orby operator assistant: streamed assistant turns,
      conversation threads, product knowledge-base search, and the tool-action
      approval gate. Available to signed-in operators only (dashboard session
      auth — API-key requests are rejected).
paths:
  /api/v1/campaigns/{id}/steps:
    get:
      tags:
        - Campaigns
      summary: List a campaign's drip steps
      description: >-
        Returns the ordered drip-sequence steps configured for a campaign — each
        step's send delay, channel, message template, optional email subject,
        and any branching condition. Steps come back sorted by their `order`.
        Use it to render or pre-fill the drip builder. Read-only; returns 404
        when the campaign does not exist.
      parameters:
        - schema:
            type: string
          in: path
          name: id
          required: true
      responses:
        '200':
          description: The campaign's drip steps, ordered by `order`.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/CampaignDripStep'
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
        '404':
          description: Campaign not found.
components:
  schemas:
    CampaignDripStep:
      type: object
      description: >-
        One step in a campaign's drip (multi-step) sequence — its send delay,
        channel, message template, and optional gating condition.
      required:
        - order
        - delay_minutes
        - channel
        - template
      properties:
        id:
          type: string
          description: Step id. Omit when creating a step; the server assigns one on save.
        order:
          type: integer
          minimum: 0
          description: >-
            Zero-based position of the step within the sequence. Steps are
            returned sorted by this value.
        delay_minutes:
          type: integer
          minimum: 0
          maximum: 525600
          description: >-
            Minutes to wait, relative to the previous step, before this step
            sends. Capped at one year (525600).
        delay_unit:
          type: string
          enum:
            - minutes
            - hours
            - days
            - weeks
          description: >-
            Optional unit for `delay_minutes`. When set, the server converts the
            value into minutes before persisting; when omitted the value is
            treated as already in minutes.
        channel:
          type: string
          description: >-
            Channel this step sends on (for example sms, email, whatsapp, rcs,
            push).
        template:
          type: string
          description: Message body/template rendered for this step.
        subject:
          type: string
          description: Subject line. Email steps only.
        condition:
          type: object
          description: >-
            Optional gate — only send this step when the previous step reached
            the given outcome.
          properties:
            type:
              type: string
              enum:
                - delivered
                - read
                - clicked
                - not_delivered
                - not_read
                - always
              description: >-
                Outcome the previous step must have reached for this step to
                fire. `always` sends unconditionally.
            timeout_minutes:
              type: integer
              description: How long to wait for the condition to be met before moving on.
    ResponseMeta:
      type: object
      required:
        - request_id
        - timestamp
      additionalProperties: false
      properties:
        request_id:
          type: string
          description: Unique request identifier (also returned as X-Request-Id header)
        timestamp:
          type: string
          format: date-time
        docs_url:
          type: string
          format: uri
          nullable: true
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Dashboard JWT token from Clerk
    ApiKey:
      type: apiKey
      name: X-API-Key
      in: header
      description: Server-to-server API key (dv_live_sk_*)

````