Tests

List learnings

The account's learnings, and the proposals nobody has accepted or dismissed.

GET
/api/v1/learnings

Each learning is a statement of why, scoped on taxonomy Values, with its status history and the evidence the app computed. Proposals are drafts from concluded Tests and strong Traits; accept one by POSTing it with its proposal_key.

Requires a key with read scope or higher.

MCP: meta_list_learnings.

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.

Query Parameters

status?string
Value in"hypothesis""supported""refuted""retired"
dimension?string
Value in"angle""persona""awareness""offer""offer_type""pain""season""asset_type""format""hook""headline_tactic""talent""visual"
value_id?string

A Value id, or a closed Dimension's word.

Lengthlength <= 100
source?string
Value in"test""trait""analysis""agent""human"
include_proposals?boolean
Defaulttrue

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 GET 'https://winandscale.com/api/v1/learnings'
Example Response
{}