Reference

`landing`

Base path: /api/v1/landing

The landing module covers landing-page generation, hosting on a 10ex subdomain (or your custom domain), embedded capture forms, and conversion analytics. It pairs with the webinars and marketing modules so an end-to-end funnel (page -> form -> sequence) is one workflow. Resources include pages, page versions, form embeds, custom domains, and conversion events. Schemas live in app/modules/landing/schemas.py.

What you can do with the landing API

Generate a landing page from a brief and brand knowledge
Iterate on copy and layout via versioned drafts
Publish a page to a 10ex subdomain or your custom domain
Embed a CRM-backed capture form on the page
Track impressions, form submissions, and downstream conversion
Archive an old page without breaking analytics history

Common operations

Create a draft page from a campaign or webinar context
Update copy, hero image, or form configuration on a draft
Publish a draft to a live URL
Fetch conversion metrics for a page over a date range
Configure a custom domain CNAME and verify TLS provisioning
Archive a page when its campaign ends

Authentication & scoping

Workspace-scoped via API key in the Authorization: Bearer tnx_... header. Public page rendering is unauthenticated by design; only the management endpoints require credentials.

Pagination & filtering

Page list endpoints paginate cursor-style with filters by status (draft, live, archived) and campaign. See Pagination.

What you can do with the landing API for funnel analytics

Each page emits view, form-submit, and downstream-conversion events that the dashboard module rolls up. Combine with crm to see which pages drive segment growth, and with marketing to attribute campaign spend to landing-page conversion.

MCP equivalents

MCP prompt

generate_landing_page({ brief: "Webinar registration page", brand_id, event_id })