Launches

Create lead form

Create an instant (lead) form on the Page.

POST
/api/v1/lead-forms

Spends nothing until an ad opens it. A published form cannot be edited; a change is a new form. Send an Idempotency-Key: a retry would otherwise create a second form.

Requires a key with write scope or higher.

MCP: meta_create_lead_form.

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.

Header Parameters

Idempotency-Key?string

Any unique string up to 256 characters. A retry with the same key and body replays the first success (Idempotency-Replay: true) instead of doing the work twice; the same key with a different body is refused.

Lengthlength <= 256

Request Body

application/json
  1. body
name*string
Length1 <= length <= 200
locale?string

Meta's form locale, e.g. EN_US, PL_PL. Default: the Page's.

Match^[A-Za-z]{2}_[A-Za-z]{2}$
questions*array<>
Items1 <= items <= 15
privacy_policy*
intro?

The intro screen.

thank_you?

The screen after submit.

higher_intent?boolean
Defaulttrue
page_id?string

Omit for the workspace's default Page.

Match^\d+$

Response Body

Created. The body is the tool's own result — the same payload the MCP tool returns.

application/json
  1. response
Example Request
curl -X POST 'https://winandscale.com/api/v1/lead-forms' \  -H 'Content-Type: application/json' \  -d '{  "name": "string",  "questions": [    {      "type": "FULL_NAME"    }  ],  "privacy_policy": {    "url": "http://example.com"  }}'
Example Response
{}