Skip to main content
POST
Create landing

Authorizations

Authorization
string
header
required

Workspace-scoped token sent in the Authorization header as Bearer . Access depends on the credential's allowed operations, read or write scope, and workspace subscription. Use an API key issued in the tracker for Public API v1. MCP uses separate OAuth credentials.

Body

application/json
name
string
required
Required string length: 1 - 160
url
string
required

Public HTTPS URL template, trimmed before saving. Supports tracker macros such as {click_id} and {token1:hash} through {token15:hash} for short token codes.

Required string length: 1 - 2048
Pattern: ^\s*[hH][tT][tT][pP][sS]://
country
string
required

Supported ISO 3166-1 alpha-2 country code, case-insensitive and trimmed. ZZ, Global, and an empty string normalize to ZZ (Global). This controls asset compatibility, not visitor filtering.

Response

Created landing id

ok
enum<boolean>
required
Available options:
true
data
object
required