What Leadpages exposes
I get programmatic access to Leadpages through an official MCP server, a REST API, and native integrations with ChatGPT, Claude, Gemini, and Perplexity. My API covers landing pages, leads, forms, analytics, and account data, with OpenAPI spec published at leadpages.com/openapi.json. Authentication supports both OAuth and API keys, so I can pick session-based flows for user-facing apps or static keys for backend jobs. The MCP server at leadpages.com/developers/mcp lets my LLM agents query and manage pages directly without custom glue code. Zapier and Make connectors are available for no-code workflows across thousands of downstream apps. Webhook availability is not documented in my data, so I would confirm event delivery options against the developer docs before relying on push notifications.
Pricing, limits, and integration
Two auth methods, and the choice affects which plan you need. An API key as a Bearer token (the lp_ prefix) is available on the Pro plan and up. If you are on a lower tier, OAuth 2.0 is open on every plan, so you can still build programmatic access without paying up to the Pro tier. I would default to OAuth unless you specifically want a static key for a server-to-server job.
Eight endpoint groups define the surface: Pages, Sites, Assets, Blogs, Analytics, Forms, Domains, and Brand Kits. Analytics exposes heatmaps and scroll-depth data, which is unusually deep for a landing-page tool. Forms gives me submission access and full lead export, so the leads I capture are mine to pull into a CRM or warehouse rather than trapped in the dashboard.
Domains covers custom-domain management and SSL programmatically, which is handy when an agent or script spins up a new site and needs it live on a real domain. I have not found documented webhooks or first-party SDKs, so plan on polling and your own HTTP client rather than push events or a prebuilt library.
How much does the Leadpages API actually cost?
Leadpages publishes an API, but per-tier gating wasn't extracted automatically.
- Most likely scenario: API access is either included in all paid plans, or it's gated to higher tiers and we need to verify on the live docs page.
- Until verified, treat the question "which plan unlocks the API" as open. Don't budget on the assumption it's free with the cheapest paid plan.
Leadpages subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| HTML Pub - Starter | $10 | $8 |
| HTML Pub - Pro | $29 | $23.2 |
| HTML Pub - Business | $49 | $39.2 |
| Leadpages - Grow | $99 | $39.2 |
| Leadpages - Optimize | $199 | $159.2 |
| Leadpages - Scale | $399 | $319.2 |
⚠ Per-tier API gating not yet structured for Leadpages. Confirm which plans unlock API access on the live docs.
Source: leadpages.com/pricing. Verified 2026-06-07.
API at a glance
Which AI clients can read Leadpages data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Leadpages specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Connect via the Leadpages MCP URL; OAuth 2.0 PKCE browser sign-in, no API key. |
| Claude Code | Native MCP | Add the https://mcp.leadpages.com/mcp endpoint; same OAuth browser sign-in. |
| ChatGPT | Native MCP | Supported on a paid ChatGPT plan via custom connectors. |
| Cursor | Native MCP | Add the MCP server in Cursor settings; OAuth browser sign-in. |
| n8n | Native MCP | Use the dedicated SSE transport for n8n automation flows. |
Leadpages also has an MCP server
If you're wiring Leadpages into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Leadpages MCP pageWhat you can build with the Leadpages API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Leadpages into your daily workflow
- Pull a digest of fresh activity into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Leadpages reporting at scale
- White-label Leadpages data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Leadpages UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Leadpages
- Real-time sync into your warehouse on a cron
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Leadpages data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Leadpages API docs: https://leadpages.com/developers/docs curl -X GET "https://leadpages.com/<your-endpoint>" \ -H "Authorization: Bearer $TOKEN" \ -H "Accept: application/json" | jq .
Template only. Endpoint paths, exact base URL, and auth header format come from leadpages.com/developers/docs.
Limits and gotchas
- OpenAPI is published — auto-generated clients work out of the box. Saves writing wrappers by hand.
- No official SDK detected. Plan on hitting the API directly with your HTTP client of choice.
- Rate limits: always read the docs page before scaling — the published limit is usually lower than the practical one and overages can be expensive.
- No-code fallback: Zapier and Make.com cover the common triggers if you want to skip writing API code for simple flows.
Agent-readiness verdict
Score: 8/10 on API-readiness. The Leadpages API is RESTful, predictable, and covers eight endpoint groups including the two that usually matter most to me: Forms with full lead export and Analytics with heatmaps plus scroll depth. Two auth paths help: an lp_ Bearer API key on Pro and up, or OAuth 2.0 on every plan, so lower-tier accounts are not locked out of programmatic access. I am keeping it at an 8 rather than higher because there are no documented first-party SDKs and no documented webhooks, so I would be writing my own polling and client code rather than reacting to push events. For a landing-page tool, though, this is a strong, usable surface.
Strong agent-fit for Claude workflows. Leadpages has an official MCP server and documented public API with OpenAPI spec, enabling direct integration with Claude and ChatGPT. Missing webhooks and structured outputs limits real-time automation and data parsing capabilities.
Leadpages API FAQ
Does Leadpages have a public API?+
What auth does the Leadpages API use?+
Is there an OpenAPI / Swagger spec I can auto-generate clients from?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Leadpages official site: https://www.leadpages.com/
- API docs: https://leadpages.com/developers/docs
- OpenAPI spec: https://www.leadpages.com/openapi.json
- MCP server: https://leadpages.com/developers/mcp
- Pricing source: https://www.leadpages.com/pricing (verified 2026-06-07)
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.