List lead forms
The instant (lead) forms on the Page, with every question's key, type and options.
A live Meta read with a Page access token. The question keys are the field names a lead arrives under. Pass a form's id as copy.lead_form_id to POST /api/v1/launches.
Requires a key with read scope or higher.
MCP: meta_list_lead_forms.
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.
page_id?stringOmit for the workspace's default Page.
^\d+$status?string"ACTIVE""ACTIVE""ARCHIVED""all"Success. The body is the tool's own result — the same payload the MCP tool returns.
application/json- response
curl -X GET 'https://winandscale.com/api/v1/lead-forms'{}