Answer merge suggestion
Merge two approved Values the reconcile pass read as one idea, or keep them apart.
decision: merge folds the suggestion's mergeId into its keepId (irreversible); keep_apart is remembered and the pair is never suggested again. Open suggestions are mergeSuggestions on GET /api/v1/taxonomy.
Requires a key with write scope or higher.
MCP: meta_answer_merge_suggestion.
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.
suggestionId*stringA merge suggestion id, from mergeSuggestions on GET /api/v1/taxonomy.
uuidapplication/json- body
decision*string"merge""keep_apart"Success. The body is the tool's own result — the same payload the MCP tool returns.
application/json- response
curl -X POST 'https://winandscale.com/api/v1/taxonomy/merge-suggestions/497f6eca-6276-4993-bfeb-53cbbbba6f08/answer' \ -H 'Content-Type: application/json' \ -d '{ "decision": "merge"}'{}