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

# Re-deliver a message's lifecycle webhook to all endpoints

> Re-dispatches the message's current-state lifecycle webhook (message.created / message.sent / message.delivered / message.failed / message.read, mapped from the persisted status) to every active subscribed endpoint, reusing the live send pipeline's signing + retry path. Returns 202 with the resolved event type and the number of endpoints the replay was enqueued against (0 when no active endpoint subscribes). The deliveries land asynchronously and surface in the message-detail Webhook Fan-out card. Distinct from the webhook-endpoint-scoped POST /webhooks/{id}/deliveries/{deliveryId}/replay, which re-fires a single stored delivery to one endpoint.



## OpenAPI

````yaml /openapi.yaml post /api/v1/messages/{id}/replay-webhook
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
paths:
  /api/v1/messages/{id}/replay-webhook:
    post:
      tags:
        - Messages
      summary: Re-deliver a message's lifecycle webhook to all endpoints
      description: >-
        Re-dispatches the message's current-state lifecycle webhook
        (message.created / message.sent / message.delivered / message.failed /
        message.read, mapped from the persisted status) to every active
        subscribed endpoint, reusing the live send pipeline's signing + retry
        path. Returns 202 with the resolved event type and the number of
        endpoints the replay was enqueued against (0 when no active endpoint
        subscribes). The deliveries land asynchronously and surface in the
        message-detail Webhook Fan-out card. Distinct from the
        webhook-endpoint-scoped POST
        /webhooks/{id}/deliveries/{deliveryId}/replay, which re-fires a single
        stored delivery to one endpoint.
      parameters:
        - schema:
            type: string
            pattern: ^msg_[0-9a-f]{32}$
          in: path
          name: id
          required: true
      responses:
        '202':
          description: Default Response
components:
  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_*)

````