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

# Preview quiet-hours dispatch decision

> Returns whether a send to the given recipient on the given channel would be allowed right now under the universal quiet-hours gate (TCPA dialing-window for voice, 08:00–21:00 baseline for SMS / RCS / Telegram / Viber, 09:00–21:00 for WhatsApp / Meta channels, configurable per-org). Read-only — does not perform a send. The `next_allowed_at` field on a blocked result is the DST-safe ISO timestamp of the next moment the gate would pass.



## OpenAPI

````yaml /openapi.yaml get /api/v1/compliance/quiet-hours/preview
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/compliance/quiet-hours/preview:
    get:
      tags:
        - Compliance
      summary: Preview quiet-hours dispatch decision
      description: >-
        Returns whether a send to the given recipient on the given channel would
        be allowed right now under the universal quiet-hours gate (TCPA
        dialing-window for voice, 08:00–21:00 baseline for SMS / RCS / Telegram
        / Viber, 09:00–21:00 for WhatsApp / Meta channels, configurable
        per-org). Read-only — does not perform a send. The `next_allowed_at`
        field on a blocked result is the DST-safe ISO timestamp of the next
        moment the gate would pass.
      parameters:
        - schema:
            type: string
          in: query
          name: phone
          required: true
          description: E.164 recipient phone number (e.g. +14155551234).
        - schema:
            type: string
            enum:
              - sms
              - mms
              - whatsapp
              - rcs
              - viber
              - telegram
              - voice
              - email
              - instagram
              - messenger
              - line
              - apple_messages
              - fax
              - push
              - web_chat
          in: query
          name: channel
          required: true
          description: Channel of the prospective send.
        - schema:
            type: string
          in: query
          name: timezone_override
          required: false
          description: >-
            Optional IANA timezone (e.g. America/New_York) overriding the
            area-code resolution. Useful when the recipient's tz is known from a
            CRM record.
      responses:
        '200':
          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_*)

````