Set thresholds
Change the goal, targets and funnel every report is judged against.
Only the fields sent change; null removes an override. Amounts are in the account currency. Returns the thresholds now in force. Moves no money.
Requires a key with write scope or higher.
MCP: meta_set_thresholds.
bearerAuthAuthorizationBearer <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— everythingwritecan. No operation requires more thanwritetoday.
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.
application/json- body
goal_event?|nullcampaign_goals?cost_per_result?funnel_steps?array<>|nullmin_spend_validate?number0 < valuemin_spend_scale?number0 < valuecpa_cut?number0 < valueroas_break_even?number0 < valueroas_early_kill?number0 < valueroas_scale?number0 < valueSuccess. The body is the tool's own result — the same payload the MCP tool returns.
application/json- response
curl -X PATCH 'https://winandscale.com/api/v1/thresholds' \ -H 'Content-Type: application/json' \ -d '{}'{}