Create a new internal page in the workspace. By default, creating a page without references to a funnel or show page step will create a standalone landing page.

You can optionally attach the page to a funnel by providing either:

• funnel.funnel_id: Creates a new show page step in the specified funnel. When provided without show_page_step_id, the page is added as the last step of the funnel, positioned after the currently last page.
• funnel.show_page_step_id: Swaps the referenced step to point at this newly created page. The page previously linked to that step becomes an orphan (kept in the workspace, no longer linked to any step).

sort_order (optional, top-level): Controls the zero-based position within the funnel when creating with funnel.funnel_id. 0 inserts before the first existing step; omit to append at the end. Out-of-bounds values (negative or greater than the current step count) return 422. sort_order is ignored when funnel.show_page_step_id is used — the swap target's current position is preserved.

funnel.after_show_page_step_id (optional, with funnel.funnel_id): Insert the new step right after the referenced show page step — also places the page inside a split branch. Alternative to sort_order. An id that does not resolve to a step in the funnel returns 400.

To also attach products to the page's checkout step in the same call, pass show_page_step.product_ids: [...] (sibling of funnel). This is the only way to set products at create time — the legacy funnel.products shape is rejected with a 400. Products attachment is additive and all-or-nothing: any unresolved id fails the whole request and the page is not created.

Order bumps: pass show_page_step.bumps: [{product_id, preheadline}] (same semantics as product_ids) to attach products as order bumps instead of main products, each with its own optional preheadline — the line of copy shown above that bump's offer. A product may appear in only one of the two blocks per request; naming it in both returns a 400.

external_url is rejected — to create an externally-hosted (SDK) page use POST /api/v2/workspaces/:workspace_id/pages/external.