Landing pages

The Landing API manages campaign pages and their statistics. Endpoints are shown with the complete /v2 prefix even where the older page omitted the leading slash.

Endpoints

Method	Path	Description
GET	/v2/landings	List landing pages.
GET	/v2/landings/{landingId}	Read a landing page.
POST	/v2/landings	Create a landing page.
PUT	/v2/landings/{landingId}	Update the page data.
DELETE	/v2/landings/{landingId}	Delete a landing page.

The collection response is paginated according to the shared pagination rules.

Data type

{
  "id": "landing_abc123",
  "name": "Welcome page",
  "views": {
    "2026": 6,
    "2026-10": 4,
    "2026-10-05": 2,
    "2026-10-05 09:00:00": 1
  },
  "link": "https://landing.ip1.net/landing_abc123",
  "shortLink": "https://url.ip1.net/example",
  "lastModified": "2026-10-05T08:03:21Z",
  "elements": [
    {
      "type": "Title",
      "id": "element_abc123",
      "order": 0,
      "backgroundColor": "#f7f7f7",
      "foregroundColor": "#111111",
      "padding": "2",
      "margin": "0",
      "textAlignment": "Center",
      "font": "Roboto",
      "content": "Welcome",
      "level": 1,
      "bold": false,
      "italic": false,
      "underline": false
    }
  ]
}

Fields

Field	Type	Description
id	string	Page ID.
name	string	Internal name.
views	object	Views grouped by year, month, day and hour.
link	string	Public URL.
shortLink	string	Short URL suitable for use in SMS.
lastModified	string	Latest change in ISO 8601.
elements	object[]	Page content elements.

According to the published documentation, PUT replaces the page’s other data while preserving elements, views and links. Use the element endpoints for content elements.

Implementation guidance

• treat link and shortLink as server-generated values
• do not include personal data in the page name or URL
• test the page on mobile before using the link in a send
• ensure the message, sender and landing page are consistent
• measure conversion against the campaign goal, not only page views