Landing templates
Account-token (and partner) CRUD for campaign landing-page templates (campaign/template/landing-page/*, authentication, no throttle).
Account-token (and partner) CRUD for campaign landing-page templates (campaign/template/landing-page/*, authentication, no throttle). Endpoints: create, list (dual-mode: campaign-flow dropdown vs paginated account-level tab with usage counts; partners can scope by account_id), preview (resolve draft HTML against a store), update (copy-on-write for globals; note enable_direct_to_* accepted-but-not-persisted), and get-by-id (optional store/preview placeholder resolution). Templates must belong to the caller's company or be global. Called by the landing-page editor and the account Landing Page Templates tab.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
POST — Create a new campaign landing-page template owned by the caller's company.
POST — Update an existing landing-page template (title, manager emails, HTML/JSON content, editor mode).
Updated 14 days ago