> ## 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. # Check for overlapping scheduled campaigns > Return already-scheduled, running, or paused campaigns that target an overlapping audience on the same channel within a time window around a proposed send time, so the wizard can warn about audience fatigue before an operator commits a schedule. Advisory and read-only — it never blocks create or update; the caller decides whether to warn based on the returned conflicts. An empty conflicts list is the no-fatigue result. ## OpenAPI ````yaml /openapi.yaml post /api/v1/campaigns/check-schedule-conflicts 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/check-schedule-conflicts: post: tags: - Campaigns summary: Check for overlapping scheduled campaigns description: >- Return already-scheduled, running, or paused campaigns that target an overlapping audience on the same channel within a time window around a proposed send time, so the wizard can warn about audience fatigue before an operator commits a schedule. Advisory and read-only — it never blocks create or update; the caller decides whether to warn based on the returned conflicts. An empty conflicts list is the no-fatigue result. requestBody: required: true content: application/json: schema: type: object required: - scheduled_at - channel properties: scheduled_at: type: string format: date-time description: Proposed send time (ISO 8601) to check conflicts around. audience_type: type: string enum: - all - list - segment - csv - manual default: all description: How the campaign's audience is selected. audience_id: type: string minLength: 1 maxLength: 128 description: List or segment id the campaign targets, when applicable. channel: type: string enum: - sms - mms - whatsapp - email - rcs - viber - voice - push - instagram - messenger - line - telegram - fax - kakao - zalo - wechat description: Channel to scope the conflict scan to. window_hours: type: integer minimum: 1 maximum: 720 description: >- Half-window (in hours) around scheduled_at to scan. Defaults to 72; capped at 720 (30 days). exclude_campaign_id: type: string minLength: 1 maxLength: 128 description: >- Campaign id to exclude so an edited campaign doesn't conflict with itself. example: scheduled_at: '2026-08-10T15:00:00.000Z' audience_type: segment audience_id: seg_newsignups channel: sms window_hours: 72 responses: '200': description: Overlapping campaigns near the proposed send time content: application/json: schema: type: object description: Overlapping campaigns near the proposed send time properties: data: type: object properties: window_hours: type: integer scheduled_at: type: string format: date-time channel: type: string conflicts: type: array items: type: object additionalProperties: true description: >- A conflicting campaign (id, name, status, scheduled_at, audience). conflict_count: type: integer meta: type: object properties: request_id: type: string description: >- Unique request identifier (also returned in X-Request-Id header) timestamp: type: string format: date-time description: ISO 8601 UTC timestamp of the response example: data: window_hours: 72 scheduled_at: '2026-08-10T15:00:00.000Z' channel: sms conflicts: - id: cmp_1a2b3c name: August Promo status: scheduled scheduled_at: '2026-08-10T09:00:00.000Z' conflict_count: 1 meta: request_id: req_7c1e9a2b3f timestamp: '2026-08-02T14:23:11.000Z' 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_*) ````