Skip to main content
The LanderLab API gives you programmatic access to your entire account. You can create and publish landers, pull lead data, read analytics, manage A/B test variants, configure integrations, and more, all over HTTP. If you prefer working in plain English instead of writing raw API calls, the MCP server connects your AI assistant directly to LanderLab using the same underlying API.

​
Base URL

All API requests go to:
The current API version is v2. Every endpoint is prefixed with /api/v2/.

​
Authentication

The API uses API key authentication. Include your key in the X-API-Key header on every request.
Your key starts with ll_live_ and is tied to your organization. All requests are scoped to the organization the key belongs to, so you do not need to pass an organization ID separately in most calls.
API keys are shown only once at creation. If you lose yours, you need to generate a new one. See Generate an API Key for steps.

​
Error responses

All endpoints return standard HTTP status codes. Error responses include an error string in the response body with a description of the problem.

​
Resource Groups

The API is organized around the following resource groups. Each group maps to a section in the API reference.

​
Workspaces

List, create, and rename workspaces within your organization. Workspaces are the top-level container for landers, leads, and domains.

​
Landers

Manage landing pages: list, create, rename, publish, unpublish, and delete. Publishing requires a domain and path and will return a 400 if plan limits are exceeded or the path is already taken. Deleting a lander removes all associated variants, files, and integrations permanently.

​
A/B Testing (Variants)

Each lander has one or more variants. The master variant is the one that receives traffic when A/B testing is off. When A/B testing is enabled, traffic is split across variants according to the weights you set. You cannot delete the master variant. Promote a different variant to master first.

​
Editor

Load and save the HTML content and settings for a specific variant. Saving HTML handles base64 image extraction and versioning automatically.

​
Leads

Pull leads at workspace or organization level. Leads are paginated and can be filtered by date range, status (complete or partial), lander, and search query. The maximum page size is 1000 per request. The lead schema endpoints return a Draft-07 JSON Schema describing all possible fields a lead from that lander can contain, including form fields, quiz answers, system fields, and integration fields.

​
Analytics

A single flexible endpoint covers all analytics needs. Filter by workspace, lander, or variant. The most specific filter wins: if you pass variantIds, workspace and lander filters are ignored. Required parameters: startDate, endDate, timezone (IANA format, e.g. America/New_York). Optional filters: workspaceIds, landerIds, variantIds. Group by: date, lander, variant, or workspace. Defaults to date.

​
Domains

List domains at workspace or organization level.

​
Folders

Organize landers into folders within a workspace.

​
Integrations

Create and list org-level integrations, then enable or disable them per lander. OAuth-based integrations (Mailchimp, HubSpot, Google Sheets, AWeber) require an interactive OAuth flow and cannot be created via the API directly.

​
OpenAPI Spec and Interactive Docs

The full OpenAPI 3.1 spec is available at:
Interactive API documentation (with a built-in request tester) is at:

​
Using the API with an AI Assistant (MCP)

If you want to manage your LanderLab account using plain English instead of writing API calls, the LanderLab MCP server is built on the same API and exposes 30+ tools to any MCP-compatible AI assistant, including Claude, ChatGPT, Cursor, and Windsurf. The MCP server URL is:
It uses the same X-API-Key header for authentication. See Connect AI Assistants via MCP for setup instructions.