September updates: landing pages from your AI assistant chat, a public API and the post-submission message
September was a busy month. In short: GetLanding now works right inside your AI assistant’s chat, the platform has a public API for integrations and automations, the message visitors see after submitting a form can be changed with a single sentence to the AI, and SalesDrive now shows which landing page a lead came from. Here is everything, one by one.
🤖 Landing pages straight from your AI assistant chat
GetLanding now works right in your Claude, ChatGPT, Cursor and other AI assistant chats thanks to our MCP server, which plugs into the assistant as a connector. Describe your business in the chat, and the assistant will create a landing page, make edits, connect a domain and show you incoming leads. Prices are the same as in the dashboard, and the assistant never sees your password: you approve access on a consent screen and can revoke it at any time.
How to connect and what you can do from the chat — in a separate post: GetLanding in AI assistants →
🔌 Public API
Everything you do in the dashboard can now be done with a request from your own system: create and edit landing pages, configure forms, connect domains and pull leads. This makes GetLanding a building block for deep integrations and your own automations — for example, n8n workflows or similar services.
- A key in a minute. Click “API keys” in the dashboard header, enter a name and click “Create key”. The key is shown once; you can have up to 10 active keys, and any of them can be revoked instantly. A key grants full access to your account, so treat it like a password.
- A landing page in three requests: draft (free) → photos and videos → generation. UAH 135 is charged only after a successful generation, and retrying with the same slug won’t create a duplicate.
- Two ways to edit: an instruction for the AI (UAH 45, charged only on success) or a full HTML replacement — free. Before every change the previous version goes into history (last 10), and restoring is free.
- Forms and product catalog: check that a form works, add or disable a field, change the post-submission message, manage products for order forms. All free.
- Domains and files: connect a custom domain with ready-made DNS instructions and certificate status; jpg/png/webp images up to 2 MB, gif up to 10 MB, mp4 video up to 50 MB. SVG is not accepted via the API — the format can contain code.
- Leads into your CRM. Retrieval is cursor-based: every lead arrives exactly once, with nothing lost or duplicated, even if your system polls irregularly. A lead’s status (new, in progress, won, lost) can also be changed by request. Email, Telegram and SalesDrive keep working as before.
- OAuth 2.1 for apps. If you build an app for other GetLanding customers, they don’t have to hand you their keys: they see a consent screen listing the permissions and click “Allow”. All grants are listed on the new “Connected apps” page, and revoking takes effect instantly.
- Limits: up to 120 requests per minute per account, of which up to 10 can be generations and AI edits. A bug in someone else’s code won’t drain your balance.
Documentation lives at app.getlanding.online/api/docs. Paste your key via Authorize, and any request can be run right from the browser. You can also download the OpenAPI spec and generate a client for your language. Keep in mind: generating from the docs is real and paid.
💬 The post-submission message — now edited by AI
When a visitor clicks “Submit”, they see a short confirmation, something like “Thank you! We’ll get in touch with you soon.” It’s the last thing a customer reads on your landing page, and now it can be changed with a single sentence.
Open your landing page, click “Edit with AI” and write, for example:
Change the message after form submission to “Thanks! We’ll call you back within an hour.”
This is a regular AI edit — UAH 45. The message is a single line of up to 300 characters.
Why editing it in the code didn’t work before. The message is sent by the server, in response to the same request that accepts the lead and puts it into your CRM. The page only displays what comes back, so text typed into the HTML changed nothing.
Check your page if it was created before July. Since the July update the AI writes its own confirmation in the landing page’s language. Older pages show the built-in English default even on non-English pages, and regenerating doesn’t fix it. One AI edit is enough.
A few more details:
- Version history remembers this message too. Restore a version and you get the message that was active back then (except for versions saved before this update).
- Changing only the message doesn’t create a new version. To bring back the previous text, just ask the AI again.
- Submission errors in plain language. If a lead couldn’t be accepted, the visitor sees a short message in the page’s language, and the “Submit” button becomes active again. This works on pages generated after the update and wherever the AI has updated the form code.
🔗 SalesDrive: see which landing page a lead came from
If your landing page is connected to SalesDrive, GetLanding now automatically
fills the “Website” field (sajt in SalesDrive) of every lead with the
landing page’s domain. If you run several sites at once and their leads end up
in one CRM, you can now see right away which page worked.
- Your own value. Open “Notifications & integrations” → “Field mapping” and pick the “Website (sajt)” key for the form field you need. Your choice takes priority.
- No lead gets lost. If SalesDrive rejects the auto-filled field, we immediately resend the lead without it. You’ll see a warning about this when sending a “Test lead”.
Thank you for being with us 💙 Great landing pages and plenty of leads to you!