Tests

Update learning

Change a learning's statement, scope or status. Status moves are appended.

PATCH
/api/v1/learnings/{learningId}

Supported or refuted without a test_id needs a reason. Retire with status retired.

Requires a key with write scope or higher.

MCP: meta_update_learning.

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

learningId*string

A learning id, from GET /api/v1/learnings.

Formatuuid

Request Body

application/json
  1. body
statement?string
Length1 <= length <= 600
observation?|null
implication?|null
scope?array<>
Itemsitems <= 8
status?string
Value in"hypothesis""supported""refuted""retired"
reason?string
Lengthlength <= 400
test_id?string
Match^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
Formatuuid
agent?string
Lengthlength <= 40

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/learnings/497f6eca-6276-4993-bfeb-53cbbbba6f08' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{}