Landing Pages API
The landing pages API 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 update public pages safely.
Manage Landing Pages
Landing pages are Mailrith-hosted subscriber capture pages. They can include page content, generated token-based public URLs, optional Pro custom-subdomain homepages and slugs, 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 requiring a user to click through the app.
Landing pages often depend on tags, custom fields, and form-style capture settings. Review those dependencies before you create or update pages programmatically.
- List existing landing pages before you create replacements during migration work.
- Confirm that the 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 you send traffic to the page. The test succeeds when the page loads, accepts a test subscriber, and applies the expected fields, tags, and consent choices.
- Do not delete an old landing page until old links, ads, and embeds have been retired.
- List landing pages when an integration needs an inventory of 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 after 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 generated public URL and page definition. Pro workspaces can also set customPath, shown as Custom Slug in the app, but only after the workspace has a verified landing page subdomain. Workspace settings control which landing page opens directly at the subdomain homepage.
When a visitor subscribes through a landing page form, Mailrith can send a landing_page.submitted webhook event to integrations such as Zapier.
Landing page access uses landing_pages:read and landing_pages:write scopes, which are separate from the forms scopes.
/v1/landing-pages List landing pages
Returns landing pages from 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 from the authenticated workspace.
View Schema /v1/landing-pages/{landing_page_id} Update a landing page
Updates an existing hosted landing page without creating a new landing page.
View Schema /v1/landing-pages/{landing_page_id} Delete a landing page
Deletes a landing page from the authenticated workspace.
View Schema /v1/landing-pages/{landing_page_id}/submissions List landing page submissions
Returns recent real submissions for one landing page, including the subscriber who submitted the landing page. Requires both `landing_pages:read` and `subscribers:read`.
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 pages. A programmatic update can immediately affect ad traffic, SEO previews, analytics, and subscriber capture.
Before you delete or replace a landing page, confirm where the URL is linked, which tags the page applies, which custom fields the page collects, and what fallback plan you will use if old traffic still arrives.
- Update 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 descriptive so users can identify each page in the Mailrith app. On Pro workspaces, keep custom slugs stable after a page is shared.
- After you change 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.