> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revcenter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Launch a campaign

> The explicit go-live step. Starts the staged campaign at the provider and flips it to `live`.

The call is the approval: who launched it and when are stamped on the campaign row for the audit trail. Only campaigns sitting in `awaiting_launch` can be launched — anything else is a `409`. On provider failure the campaign moves to `failed` with the provider's message attached.



## OpenAPI

````yaml /openapi.json post /api/campaigns/{id}/launch
openapi: 3.1.0
info:
  title: Revcenter API
  description: >-
    Search, enrich, and activate people and companies. Two authentication
    surfaces share one host: the bearer-token API under `/v1` for
    server-to-server and agent use, and the workspace-session API under `/api`
    that the Revcenter app itself runs on.
  version: '2026-08-12'
servers:
  - url: https://api.revcenter.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Search
    description: Web search, search runs, results, exports, and shareable shortlists.
  - name: People
    description: Person search, profile enrichment, and the workspace contact pool.
  - name: Companies
    description: Company search, company enrichment, and org-chart people.
  - name: Campaigns
    description: Plan, publish, and launch outbound sequences on Smartlead and HeyReach.
  - name: Account
    description: Health, usage totals, and cost events.
paths:
  /api/campaigns/{id}/launch:
    post:
      tags:
        - Campaigns
      summary: Launch a campaign
      description: >-
        The explicit go-live step. Starts the staged campaign at the provider
        and flips it to `live`.


        The call is the approval: who launched it and when are stamped on the
        campaign row for the audit trail. Only campaigns sitting in
        `awaiting_launch` can be launched — anything else is a `409`. On
        provider failure the campaign moves to `failed` with the provider's
        message attached.
      operationId: launchCampaign
      parameters:
        - $ref: '#/components/parameters/CampaignId'
      responses:
        '200':
          description: The campaign is live.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                    examples:
                      - true
                  status:
                    type: string
                    examples:
                      - live
        '401':
          $ref: '#/components/responses/AppUnauthorized'
        '404':
          $ref: '#/components/responses/AppNotFound'
        '409':
          $ref: '#/components/responses/AppConflict'
        '424':
          $ref: '#/components/responses/AppProviderUnavailable'
        '502':
          $ref: '#/components/responses/AppUpstreamError'
      security:
        - sessionCookie: []
components:
  parameters:
    CampaignId:
      name: id
      in: path
      required: true
      description: The campaign ID.
      schema:
        type: string
        format: uuid
  responses:
    AppUnauthorized:
      description: >-
        Not signed in, no active workspace, or the account lacks the role this
        action needs. A frozen account gets `403` with code `frozen`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            signIn:
              value:
                error: Sign in required
    AppNotFound:
      description: >-
        The record does not exist, or belongs to another workspace. The two are
        deliberately indistinguishable.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            notFound:
              value:
                error: Scan not found
    AppConflict:
      description: The record is in a state that does not allow this action.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            running:
              value:
                error: Scan is already running
            notAwaiting:
              value:
                error: Campaign is not awaiting launch
    AppProviderUnavailable:
      description: >-
        A capability this action needs is not connected for the workspace. The
        `code` names which one.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            search:
              value:
                error: Search is unavailable for this workspace.
                code: search_unavailable
            scoring:
              value:
                error: AI scoring is unavailable for this workspace.
                code: ai_scoring_unavailable
            heyreach:
              value:
                error: No HeyReach API key configured — add one in Credentials.
                code: heyreach_not_configured
    AppUpstreamError:
      description: A downstream service or the database failed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            upstream:
              value:
                error: Spec extraction failed
  schemas:
    AppError:
      type: object
      description: >-
        The error shape used by every `/api` endpoint. Flatter than the `/v1`
        shape, and `code` appears only where the UI branches on it.
      properties:
        error:
          type: string
        code:
          type: string
          examples:
            - search_unavailable
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A Revcenter API key: `Authorization: Bearer rvc_live_...`. Keys are
        scoped, rate limited per key, and metered per workspace.
    sessionCookie:
      type: apiKey
      in: cookie
      name: session
      description: >-
        A signed-in workspace session, sent as a browser cookie. Requests must
        include credentials, and act on the session's active workspace.

````