Launches

Update ad set targeting

Change an existing ad set's placements and/or age range.

PATCH
/api/v1/ad-sets/{adSetId}/targeting

Only the fields sent change. A significant edit: the ad set re-enters learning, so send every targeting change for one ad set in one call. Returns before / after.

Requires a key with write scope or higher, and the approval grant.

MCP: meta_update_ad_set_targeting.

Authorization

bearerAuth
headerAuthorizationBearer <token>

An API key from Settings → API keys, sent as Authorization: Bearer rsk_….

Authorization has two independent axes.

The scope is ranked — a key satisfies any requirement at or below its own tier:

  • read — every GET.
  • write — launch ads PAUSED, sync, pull history, edit thresholds, Values, briefs, tests, swipes and research.
  • admin — everything write can. No operation requires more than write today.

There is no approve scope. It was a rung once; it is not one now, and a key requested with it is rejected.

The approval grant (can_approve) is a separate boolean, not a rung. Changing spend on Meta — activating a launch, pausing or resuming ads, retargeting an ad set, or rebuilding a launch's live creative — needs write and the grant. Keeping them on separate axes is what makes the review gate a control rather than a convention: a key that may propose is not automatically a key that may approve its own proposal.

A key reaches the one workspace — one Meta ad account — it was minted in, and stops working when the operator who minted it leaves the workspace. The same key authenticates the MCP endpoint (/api/mcp) for a headless agent, with the same scope and grant.

Path Parameters

adSetId*string

A Meta ad set id, from GET /api/v1/campaigns.

Match^\d+$

Request Body

application/json
  1. body
placements?string

facebook_instagram (default): Facebook + Instagram only — no Audience Network, Messenger, Threads or WhatsApp. automatic: Meta's Advantage+ placements, Audience Network included.

Value in"facebook_instagram""automatic"
age_min?integer
Range13 <= value <= 65
age_max?integer
Range13 <= value <= 65

Response Body

Success. The body is the tool's own result — the same payload the MCP tool returns.

application/json
  1. response
Example Request
curl -X PATCH 'https://winandscale.com/api/v1/ad-sets/string/targeting' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{}