List launches

Request

GET /launches on https://api.apogee.ad/api/v1.

Query parameters

• limit integer query optional

  Page size

  Default 50

  1 to 200

• cursor string query optional

  next_cursor of the previous page

• ad_account_id string query optional

  Meta ad account id (act_…)

  Matches ^(act_)?\d{1,32}$

• status string query optional

  One of processing, completed, failed, interrupted

Headers

• Authorization string header required

  Bearer apk_…: an API key with the scope of this route.

Response

200. A page of results: pass next_cursor as cursor for the next one, limit from 1 to 200 (default 50).

• data array of objects
  Fields of each item (8)

  • id string
  • status string

    One of processing, completed, failed, interrupted

  • name string or null
  • ad_account_id string or null
  • files object
    Fields (3)

    • total number or null
    • completed number or null
    • failed number or null
  • created_at string or null
  • completed_at string or null
  • interrupted_at string or null
• has_more boolean
• next_cursor string or null

Every answer carries X-Request-Id (give it to support), Apogee-Version: 2026-10-06, and the RateLimit and RateLimit-Policy headers.

Errors

Errors are application/problem+json with a stable code to switch on (all the codes).

Example

With your key in APOGEE_API_KEY (create one):

curl 'https://api.apogee.ad/api/v1/launches' \
  -H "Authorization: Bearer $APOGEE_API_KEY"

{
  "data": [
    {
      "id": "120200000000000001",
      "name": "Nordlicht | Spring launch",
      "ad_account_id": "act_1234567890",
      "status": "processing",
      "files": {
        "total": 3,
        "completed": 3,
        "failed": 0
      },
      "created_at": "2026-10-23T09:00:00.000Z",
      "completed_at": "2026-10-23T09:00:00.000Z",
      "interrupted_at": "2026-10-23T09:00:00.000Z"
    }
  ],
  "has_more": false,
  "next_cursor": null
}

Access and cost

In the MCP

An AI assistant does the same with this tool of the MCP server:

• list_launches: Your launches (the app's History), newest first: status, files, dates.

Related operations

• Get launch questions: POST /ad-accounts/{acc}/launch-questions
• Create launch plan: POST /launch-plans
• Get launch plan: GET /launch-plans/{id}
• Confirm launch plan: POST /launch-plans/{id}/confirm
• Get launch plan status: GET /launch-plans/{id}/status
• Get launch: GET /launches/{id}