Landing Pages API
The landing pages surface lets integrations manage hosted capture pages outside the app. This guide explains when to list, create, update, or delete landing pages, how page definitions depend on tags and fields, and how to change public pages safely.
6 min read
Manage Landing Pages
Landing pages are Mailrith-hosted subscriber capture pages with page content, public URLs, SEO settings, analytics settings, and form-backed subscriber capture.
Use the public landing pages API when an external builder, migration script, agency tool, or internal workflow needs to manage hosted pages without asking a user to click through the app.
Landing pages usually depend on tags, custom fields, and form-style capture settings. Review those dependencies before creating or updating pages programmatically.
- List existing landing pages before creating replacements during migration work.
- Confirm required tags and custom fields already exist in the workspace.
- Create or update the landing page using the public schema from API Reference.
- Store the saved landing page ID and public URL in the external system.
- Ask a Mailrith user to test the public page and subscriber submission path before sending traffic to it.
- Do not delete an old landing page until old links, ads, and embeds have been retired.
- List landing pages when an integration needs to inventory hosted capture pages.
- Create landing pages when another system owns page setup and needs to keep Mailrith in sync.
- Update landing pages when external copy, layout, SEO, analytics, or capture settings change.
- Delete landing pages only when the public page has intentionally been retired.
Endpoint Overview
GET /v1/landing-pages returns landing pages in the authenticated workspace. Item endpoints let you inspect, update, or delete one page.
POST /v1/landing-pages creates a landing page with a URL-safe slug and page definition. Build the payload from the OpenAPI schema so content, styles, and settings match what Mailrith expects.
Landing page access uses landing_pages:read and landing_pages:write scopes, separate from the forms scopes.
/v1/landing-pages List landing pages
Returns landing pages in the authenticated workspace.
View Schema /v1/landing-pages Create a landing page
Creates a hosted landing page in the authenticated workspace.
View Schema /v1/landing-pages/{landing_page_id} Get a landing page
Returns a landing page in the authenticated workspace.
View Schema /v1/landing-pages/{landing_page_id} Update a landing page
Updates an existing hosted landing page in place.
View Schema /v1/landing-pages/{landing_page_id} Delete a landing page
Deletes a landing page from the authenticated workspace.
View Schemacurl "https://api.mailrith.com/v1/landing-pages?limit=25" \
-H "Authorization: Bearer mrk_example_secret_key"Change Landing Pages Safely
Landing pages are public surfaces. A programmatic update can affect ad traffic, SEO previews, analytics, and subscriber capture immediately.
Before deleting or replacing a landing page, confirm where the URL is linked, which tags it applies, which custom fields it collects, and what the fallback plan is if old traffic still arrives.
- Prefer updating a landing page in place when public URLs must keep working.
- Create a new landing page when the new page has a different campaign, audience, or attribution purpose.
- Keep page names and slugs descriptive so users can identify them in the Mailrith app.
- After changing a landing page, open the public URL and submit a test subscriber through the real page.
Need Help Shipping an Integration?
Reach the Mailrith team if you need help planning a sync, validating a webhook flow, or troubleshooting a request.
Related Guides
Manage Mailrith capture forms from external builders, migrations, and admin tools.
Manage typed subscriber fields before syncing values, forms, segments, or migrated data.
Create signed event subscriptions for CRMs, dashboards, audits, and workflow systems.