launch

What it does

Parameters

• plan_id string required

  up to 64 characters

• confirm constant required

  true = the user said yes to the recap

  Always true

• previous_error_fixed constant optional

  true only when the user says the cause of the last failed launches on this ad account is fixed (launch_status what_to_do), or chose a change that removes it

  Always true

Example

Your assistant calls it for you when you ask in your own words. What it sends (MCP tools/call, JSON-RPC 2.0):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "launch",
    "arguments": {
      "plan_id": "7b0f3c52-4d1e-4c8a-9f61-2a5e8d3c1b90",
      "confirm": true
    }
  }
}

The same call over HTTP with an API key, for an MCP client of your own (an assistant that signs in sends its OAuth token instead):

curl -X POST https://app.apogee.ad/mcp \
  -H "Authorization: Bearer $APOGEE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"launch","arguments":{"plan_id":"7b0f3c52-4d1e-4c8a-9f61-2a5e8d3c1b90","confirm":true}}}'

confirm: true is the user's yes: send it only after showing them exactly what will happen and getting their explicit agreement.

Access and cost

In the REST API

The same thing for your own code, with an API key:

• Confirm launch plan: POST /launch-plans/{id}/confirm

Related tools

Launch: The interview, the recap, your yes, then the launch.

• get_launch_questions: The questions the app asks before every launch, in order, with the choices read from your account and a recommended answer (TikTok's and Snapchat's own with platform). Called again with the files (it reads their names with your naming convention and proposes the ads) and with the answers so far.
• prepare_launch: Prepares the launch without creating anything: the whole recap and a plan_id, valid 24 hours. Refuses while a question is open. Starts from scratch, a copied ad set and ad, or saved templates; the ads are new files (grouped by your naming convention or by hand), or existing ads reused with their post ID.
• launch_status: Follows a launch until it is finished. interrupted means an Apogee deploy cut it: check Ads Manager before launching again.
• create_campaign: Prepares a new campaign, always created paused: name, objective, budget per ad set (ABO) or per campaign (CBO, with its bid strategy). execute_action creates it after your OK.