> ## 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.

# Get campaign delivery stats

> Returns the aggregate delivery rollup for a single campaign — total recipients, how many messages were sent, delivered, failed, and read, plus the derived delivery rate and read rate. Use it to drive the campaign detail summary cards or to poll headline performance while a broadcast is running. Read-only; returns 404 when the campaign does not exist in your workspace.



## OpenAPI

````yaml /openapi.yaml get /api/v1/campaigns/{id}/stats
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}/stats:
    get:
      tags:
        - Campaigns
      summary: Get campaign delivery stats
      description: >-
        Returns the aggregate delivery rollup for a single campaign — total
        recipients, how many messages were sent, delivered, failed, and read,
        plus the derived delivery rate and read rate. Use it to drive the
        campaign detail summary cards or to poll headline performance while a
        broadcast is running. Read-only; returns 404 when the campaign does not
        exist in your workspace.
      parameters:
        - schema:
            type: string
          in: path
          name: id
          required: true
      responses:
        '200':
          description: Aggregate delivery counts and derived rates for the campaign.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      sent:
                        type: integer
                        description: Messages handed to a provider for this campaign.
                      delivered:
                        type: integer
                        description: Messages confirmed delivered.
                      failed:
                        type: integer
                        description: Messages that failed to deliver.
                      read:
                        type: integer
                        description: >-
                          Messages the recipient read or opened, on channels
                          that report reads.
                      total_recipients:
                        type: integer
                        description: Total recipients targeted by the campaign.
                      delivery_rate:
                        type: number
                        description: delivered / sent, as a fraction between 0 and 1.
                      read_rate:
                        type: number
                        description: read / delivered, as a fraction between 0 and 1.
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
              example:
                data:
                  sent: 4820
                  delivered: 4715
                  failed: 105
                  read: 3120
                  total_recipients: 4820
                  delivery_rate: 0.978
                  read_rate: 0.662
        '404':
          description: Campaign not found.
components:
  schemas:
    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_*)

````