A landing page is a focused, single-product conversion page. They're independent of the storefront catalogue — you can have a landing page with no live product (for upcoming launches), or one tied to a specific product for paid ads.

Sections (image carousels, order forms, fake visitors, countdowns, etc.) can be built through the API with the section endpoints below, or in the dashboard.

The cap applies on every create path, the API included, and counts every landing page including drafts. POST /v1/landing-pages (and POST /v1/landing-pages/generate) on a store at its limit answers 403 limit_reached. A Free-plan store can create a page only while it has an unused purchased slot; POST /v1/landing-pages marks that page is_purchased: true, which is what makes it visible on the storefront.

List landing pages. Cursor-paginated. Served fresh on every call, like GET /v1/landing-pages/{id}.

Auth: platform key with landing_pages:read, which GET /v1/landing-pages/{id} needs too. A key without it gets 403 forbidden.

An unrecognised status is ignored, returning all pages rather than a 400.

Detail with section_count.

Auth: platform key with landing_pages:write and landing_pages:read. The answer reads the page back, so with landing_pages:write alone the page is saved and the call answers 403 forbidden; the same holds for PATCH and /publish. Requires Idempotency-Key.

Slugs are made unique within your store by appending -2, -3, … An empty slug base falls back to landing- plus 6 hex characters.

Returns 200 (not 201) and the same shape as GET /v1/landing-pages/{id}. The new landing page has no sections: add them with the section endpoints below. The publish check does not run on create, so create the page as a draft and publish it once its sections are in place; a page created with status: active goes live empty.

Partial update.

PATCH validates more strictly than create: an invalid status returns 400 bad_request ("status must be active or draft") and an invalid language returns 400 ("language must be ar, fr, or en") instead of being coerced. title must still be 1 to 255 bytes. A slug sent on PATCH is normalised, unlike on create. Setting status to active runs the publish check (see /publish below). Once a page has a product, product_id: null answers 422 product_required; send another product id to switch products.

Renaming auto-regenerates slug only if you didn't pass slug explicitly. When the slug changes, by a rename or explicitly, the old address keeps working and redirects to the new one.

A page renders its sections from top to bottom. Section reads need landing_pages:read, section writes need landing_pages:write, and every write needs an Idempotency-Key.

A section carries id, section_type, sort_order and settings. Answers that read the page back (the list, reorder and PATCH) also carry created_at and updated_at. The 14 types are image, order_form, order_button, free_text, contact_button, countdown, fake_visitors, special_offer, price_display, product_offers, custom_form, image_carousel, announcement_bar and testimonials. Read GET /v1/landing-page-section-types before writing, so your settings keys match what the page renders.

Reports what a buyer would find broken on the page. Auth: landing_pages:read.

The answer carries landing_page_id, status, product_id, sections (how many were checked), publishable, blocked_by (the first blocking message, or null) and problems. Each problem has code, severity (blocking or warning) and message; problems tied to one section also carry section_id.

Publishing is refused while a blocking problem remains (see below).

Convenience: flip status to active. Equivalent to PATCH ... { status: "active" }, and refused the same way: while GET /v1/landing-pages/{id}/check reports a blocking problem, the call answers 422 page_not_publishable and the error carries the problems list. Edits that do not send status skip this check, even on a live page.

Builds a landing page from one of your products with AI. It answers 202 at once with a task to poll; a run takes about two minutes. Auth: the ai:generate scope. Keys created in the dashboard or with POST /v1/keys and third-party apps do not carry it and get 403 forbidden; Claude, ChatGPT and DZBuild Copilot connections carry it. Requires Idempotency-Key.

The answer carries task_id, size, credits_charged, eta_seconds and poll. Credits are taken when the run starts and given back when the run fails or times out. Errors: 400 bad_request (title missing or shorter than 3 characters), 402 quota_exceeded (not enough AI credits), 403 limit_reached (plan landing page limit, with limit and current), 409 already_processing (one generation per store at a time), 422 product_required, product_not_found or product_has_no_image, 429 rate_limited or too_many_concurrent, 503 provider_unavailable (no credits taken).

Poll GET /v1/landing-pages/generate/{task_id} with landing_pages:read. It answers task_id, status (processing while the page is built, then completed or failed), landing_page_id once the page exists, current_step and error. A run still processing after 10 minutes is marked failed with error timeout at the next poll, and its credits are refunded.

Hard delete. The page's sections are removed with it.

Response: { "data": { "deleted": true, "id": 42 } }.