---
title: "Authorize and start a draft campaign"
method: POST
path: "/v1/campaigns/{campaign_id}/launch"
---

# Authorize and start a draft campaign

`POST /v1/campaigns/{campaign_id}/launch`

## Request

- Base URL: `https://api.skysay.ai`
- URL: `https://api.skysay.ai/v1/campaigns/{campaign_id}/launch`
- Auth: none declared

Existing-customer or consented lists on active workspace capabilities start immediately (or at scheduled_start_at). The response carries the authorization decision: allowed, needs_review (workspace not active, voice not an enabled channel, a destination country outside the allowlist, or the custom implementation-services profile, whose every launch is reviewed) or blocked (sanctioned destination, blocked purpose, missing consent basis). Campaigns are open to every active workspace; there is no per-profile campaign switch. Contacts already on the do-not-call register are marked and never dialed.

## Path parameters

- `campaign_id` string, required

## Response `200`

Campaign with authorization and run

---

[API](https://skmtc.dev/skysay/apis/skysay-api.md) · [All operations](https://skmtc.dev/skysay/apis/skysay-api/llms.txt) · [OpenAPI document](https://skmtc.dev/skysay/apis/skysay-api/revisions/95b8c66f99aa?raw)