---
title: "Meta Ads Request Activation"
method: POST
path: "/v2/meta-ads/{launch_id}/request-activation"
tags: ["v2 - Meta Ads"]
---

# Meta Ads Request Activation

`POST /v2/meta-ads/{launch_id}/request-activation`

## Request

- Base URL: `https://api.jubjubapp.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.jubjubapp.com/v2/meta-ads/{launch_id}/request-activation`
- Auth: HTTP bearer

Ask the owner of the ad account's connection to let this ad spend.
Creates an approval row; never activates. 403 on a key without the ads
scope, 409 needs_meta_permission or no reachable owner, 422 when the
committed budget exceeds a cap or a cap is missing.

The approver is whoever owns the Meta Ads credential NOW (Tom,
2026-10-13): spend is the account owner's money. Until then the
workspace's approvers were asked, so a workspace owner could approve
spending a member's ad account. The spend approval has no off switch
while campaigns are on; while they are off it is refused with them.

## Path parameters

- `launch_id` string, required

## Headers

- `Authorization` string
- `X-JubJub-Service-Key` string
- `X-JubJub-Agent-Key` string
- `X-JubJub-Platform-Key` string
- `Origin` string
- `Referer` string
- `X-JubJub-Trial-Token` string

## Response `201`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/jubjubapp/apis/jubjub-api.md) - [All operations](https://skmtc.dev/jubjubapp/apis/jubjub-api/llms.txt) - [OpenAPI document](https://skmtc.dev/jubjubapp/apis/jubjub-api/revisions/353157b296f2?raw)