Marketing
Landing pages
Create, edit and publish landing pages from your system or from an agent. It is the same engine as the visual editor: what you do through the API looks the same in the editor and vice versa.
| GET | /v1/landing-pages | Lists pages (filter with status=draft, published or unpublished). |
| GET | /v1/landing-pages/templates | Templates available to create a page. |
| GET | /v1/landing-pages/{id} | A page with its full document (include_document=false to omit it). |
| POST | /v1/landing-pages | Creates a page from a template, written by AI, or with your own document. |
| PATCH | /v1/landing-pages/{id} | Changes title, address, settings or the whole draft. |
| POST | /v1/landing-pages/{id}/publish | Publishes the current draft. |
| POST | /v1/landing-pages/{id}/unpublish | Takes the page offline; the draft is kept. |
| GET | /v1/landing-pages/{id}/analytics | Visits, leads, WhatsApp clicks, payments and sources (days=7, 30 or 90). |
| DELETE | /v1/landing-pages/{id} | Deletes the page and takes it offline. |
Create a page
Send one of three: template, ai_description or document. With none, a blank page is created with your brand colors and font.
| Field | Description |
|---|---|
| title | Internal page name. It is also the tab title unless you set one in SEO. |
| slug | Last part of the address (summer-promo). If taken, a number is appended. |
| template | Key of a template from /v1/landing-pages/templates. |
| ai_description | What the page must achieve. AI picks the sections and writes the copy with your real business data (products, hours, WhatsApp). Requires a connected AI key or the free trial. |
| document | Editor JSON document (sections, elements, theme and SEO), as returned by GET. |
| locale | es, en or pt_BR. Defaults to your account language. |
| publish | true to publish it right away. |
Request
curl -X POST "https://recaudo.app/api/v1/landing-pages" \
-H "Authorization: Bearer sk_live_tu_secret_key" \
-H "Content-Type: application/json" \
-d '{
"title": "Promo limpieza dental",
"ai_description": "Limpieza dental a $499 en Monterrey, agenda por WhatsApp",
"publish": true
}'
Response
{
"object": "landing_page",
"data": {
"id": "8f1c2d3e-4a5b-4c6d-8e7f-9a0b1c2d3e4f",
"object": "landing_page",
"title": "Promo limpieza dental",
"slug": "promo-limpieza-dental",
"status": "published",
"locale": "es",
"template": "ai",
"url": "https://tu-negocio.recaudo.app/p/promo-limpieza-dental",
"is_home": true,
"revision": 1,
"has_unpublished_changes": false,
"settings": {},
"published_at": "2026-11-20T18:30:02+00:00",
"document": { "version": 1, "locale": "es", "theme": { … }, "meta": { … }, "sections": [ … ] }
}
}
Form element using one of your forms
The form element can use its own fields (source=page, the quick form) or one of your forms from the Forms module (source=lead_form). With lead_form the page renders that form's fields with the page design and saves every response to it.
| Field | Description |
|---|---|
| props.source | page (default) or lead_form. |
| props.lead_form_id | UUID of a published form in your account. If it is not yours, POST and PATCH respond 422 with code lead_form_not_found. |
Request
{
"id": "e4k2m9q7xa",
"type": "form",
"props": {
"source": "lead_form",
"lead_form_id": "3b6f0c1e-9d2a-4e5b-8c7d-1a2b3c4d5e6f",
"submit_label": "Quiero mi cotización",
"success_message": "¡Gracias! Te escribimos hoy mismo."
},
"items": [],
"layout": { … },
"style": { … }
}
- It runs the same as a submission on the form's own page: creates or updates the customer, applies its lists and tags, records the terms acceptance, calls its webhook and fires "Form submitted" (form.submitted) with landing_page_id and UTM.
- The page keeps its lead count and attribution (UTM, fbclid, gclid) and sends a single Lead event to Meta with the same event_id as the pixel.
- Fields arrive as f[field_0], f[field_1]… in the form's order; if it asks for terms, also f[accept_terms]=1.
- If you unpublish the form, the page shows a notice and the submission responds 422 with a clear message.
- Document: it is JSON, never HTML. Each element has type, props, style per device (desktop, tablet, mobile) and a layout in grid columns. The easiest way is to read it with GET, change what you need and send it whole with PATCH.
- Revisions: each PATCH with document increments revision. If you send revision and someone saved later (in the editor or through the API), it responds 409 and does not overwrite their changes.
- Security: rich text goes through an allowlist of tags, links only accept http, https, mailto and tel, and scripts are removed. Unknown fields are ignored.
- Plan limits: publishing more pages than your plan allows responds 403 with code limit_pages.
- AI errors: ai_unavailable (no AI key connected), ai_limit (free trial used up) and ai_failed (the AI did not answer properly; try again).
- Leads: every submitted form creates or updates the customer, fires the lead.created event to your webhooks and the "Landing page form submitted" trigger of your automations, with UTM, fbclid and gclid.
- MCP: the same actions are available as tools (create_landing_page, publish_landing_page, get_landing_page_analytics…).
Was this page helpful?
Thanks for letting us know.