> ## 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. # Reject a campaign launch pending approval > Lets a supervisor (owner or admin) reject a campaign launch that is waiting in the approval queue. Rejecting flips the campaign back to `draft` so the operator can edit and resubmit it, and records the decision (with an optional reason) on the approval row. Use it as the counterpart to the approve action for launches gated by the org's supervisor-approval policy. Requires a pending approval on a `pending_approval` campaign; returns 403 for non-supervisors, 404 when no pending approval exists, and 409 if the campaign is no longer pending approval. ## OpenAPI ````yaml /openapi.yaml post /api/v1/campaigns/{id}/reject 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}/reject: post: tags: - Campaigns summary: Reject a campaign launch pending approval description: >- Lets a supervisor (owner or admin) reject a campaign launch that is waiting in the approval queue. Rejecting flips the campaign back to `draft` so the operator can edit and resubmit it, and records the decision (with an optional reason) on the approval row. Use it as the counterpart to the approve action for launches gated by the org's supervisor-approval policy. Requires a pending approval on a `pending_approval` campaign; returns 403 for non-supervisors, 404 when no pending approval exists, and 409 if the campaign is no longer pending approval. parameters: - schema: type: string in: path name: id required: true requestBody: required: false content: application/json: schema: type: object properties: reason: type: string description: >- Optional reason shown to the operator who submitted the launch. additionalProperties: false example: reason: >- Audience includes suppressed contacts; fix the segment before resubmitting. responses: '200': description: Launch rejected; the campaign is returned to draft. content: application/json: schema: type: object properties: data: type: object properties: approval_id: type: string status: type: string description: Always "rejected". meta: type: object properties: request_id: type: string timestamp: type: string format: date-time '403': description: Only an owner or admin may reject campaign launches. '404': description: No pending approval row exists for this campaign. '409': description: >- Campaign is no longer pending approval (`CAMPAIGN_NOT_PENDING_APPROVAL`). 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_*) ````