Send test lead
Send a test lead through a form, end to end.
Meta delivers it to the lead webhook like a real lead, so it runs whatever the CRM does with one — use the operator's own phone and email. One test lead per form: pass replace_lead_id to delete the previous one first.
Requires a key with write scope or higher.
MCP: meta_send_test_lead.
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.
formId*stringA Meta instant (lead) form id, from GET /api/v1/lead-forms.
^\d+$application/json- body
answers*replace_lead_id?string^\d+$page_id?string^\d+$Created. 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/lead-forms/string/test-leads' \ -H 'Content-Type: application/json' \ -d '{ "answers": { "property1": "string", "property2": "string" }}'{}