Landing Pages API - Scalev Documentation

Use the Landing Pages API when your backend needs to create, list, update, publish, or delete Scalev landing pages. These are authenticated business endpoints. Do not call them from browser JavaScript because they require a business API key or OAuth access token. The endpoints can return Builder and HTML Mode pages. This guide documents the HTML Mode payload because it is the recommended API payload for creating page code directly. Builder request payloads are intentionally not documented and will remain that way.

Auth

Send a business API key or OAuth access token in the Authorization header:

curl https://api.scalev.com/v3/pages \
  -H "Authorization: Bearer $SCALEV_API_KEY"

Required scopes:

Action	Scope
List pages and displays	`page:list`
Read one page or display	`page:read`
Create a page	`page:create`
Update metadata, publish state, tags, and displays	`page:update`
Delete a page	`page:delete`
List stores	`store:list`
List payment methods, sales people, and product knowledge	`store:read`
List store products and variants	`product:list`, `product:read`
List store bundles and bundle price options	`bundle:list`, `bundle:read`
List payment accounts	`payment_account:list`
Manage analytics pixels and GTM containers	`fb_pixel:`, `tiktok_pixel:`, `kwai_pixel:`, `gtm:`

Endpoints

GET    /v3/pages
POST   /v3/pages
GET    /v3/pages/simplified
GET    /v3/pages/tags
GET    /v3/pages/{page_id}
PATCH  /v3/pages/{page_id}
DELETE /v3/pages/{page_id}
GET    /v3/pages/{page_id}/public
POST   /v3/pages/{page_id}/update-tags

GET    /v3/pages/{page_id}/page-displays
POST   /v3/pages/{page_id}/page-displays
GET    /v3/pages/{page_id}/page-displays/{display_id}
DELETE /v3/pages/{page_id}/page-displays/{display_id}

GET    /v3/stores/simplified
GET    /v3/stores/{store_id}/products
GET    /v3/stores/{store_id}/variants/{variant_id}
GET    /v3/stores/{store_id}/bundles
GET    /v3/stores/{store_id}/bundles/{bundle_id}
GET    /v3/stores/{store_id}/bundle-price-options/{id}
GET    /v3/stores/{store_id}/sales-people
GET    /v3/stores/{store_id}/payment-methods
GET    /v3/stores/{store_id}/payment-accounts
GET    /v3/stores/{store_id}/pages

GET    /v3/fb-standard-events
GET    /v3/tiktok-standard-events
GET    /v3/kwai-standard-events
GET    /v3/fb-pixels
POST   /v3/fb-pixels
GET    /v3/fb-pixels/{id}
PATCH  /v3/fb-pixels/{id}
DELETE /v3/fb-pixels/{id}
GET    /v3/tiktok-pixels
POST   /v3/tiktok-pixels
GET    /v3/tiktok-pixels/{id}
PATCH  /v3/tiktok-pixels/{id}
DELETE /v3/tiktok-pixels/{id}
GET    /v3/kwai-pixels
POST   /v3/kwai-pixels
GET    /v3/kwai-pixels/{id}
PATCH  /v3/kwai-pixels/{id}
DELETE /v3/kwai-pixels/{id}
GET    /v3/gtm
POST   /v3/gtm
GET    /v3/gtm/{id}
PATCH  /v3/gtm/{id}
DELETE /v3/gtm/{id}

List endpoints use cursor pagination. If has_next is true, send next_cursor on the next request. If has_previous is true, send previous_cursor to move backward.

Complete setup flow

List stores with GET /v3/stores/simplified. Use the returned numeric store id as {store_id} for authenticated business-scoped setup endpoints.
List sellable items for the store with GET /v3/stores/{store_id}/products and GET /v3/stores/{store_id}/bundles. Use product variants[].id for form_display.variant_ids, or bundle bundle_price_options[].id for form_display.bundle_price_option_ids.
Fetch one item if you need details with GET /v3/stores/{store_id}/variants/{variant_id} or GET /v3/stores/{store_id}/bundle-price-options/{id}.
List existing analytics records with GET /v3/fb-pixels, GET /v3/tiktok-pixels, GET /v3/kwai-pixels, and GET /v3/gtm. Create missing records with the matching POST endpoint.
List valid event names with GET /v3/fb-standard-events, GET /v3/tiktok-standard-events, and GET /v3/kwai-standard-events?type=client|server.
If after_submit_event is direct_to_whatsapp with fixed assignment, list handlers with GET /v3/stores/{store_id}/sales-people and send the selected id as store_sales_person_id.
Create or update the page display. Send Scalev record IDs in *_pixel_ids, gtm_id, variant_ids, bundle_price_option_ids, and store_sales_person_id.
Publish by creating the page with is_published: true, or by patching current_page_display_id on PATCH /v3/pages/{page_id}.

Custom domain setup and business-user assignment management are not part of this public v3 Landing Pages release.

HTML Mode display payload

HTML Mode uses render_mode: "html_mode" and these code fields:

html_code: body-only HTML
css_code: CSS
js_code: browser JavaScript
additional_head_code: optional extra document <head> code
csp_policy: optional Content Security Policy additions

When js_code is sent as an empty string, API responses may return it as null. Treat both null and "" as “no JavaScript” when reading page displays. css_code and additional_head_code can still round-trip as empty strings. Use additional_head_code when you need to add supported head tags directly: title, meta, link, style, script, and noscript. Scalev also creates managed head tags from convenience settings such as meta.title, meta.description, meta.thumbnail, meta.favicon, and meta.isDisabledSearchEngineCrawler. If your additional_head_code includes a conflicting title, meta, or favicon link, your additional head entry wins. meta.lang remains the source for the rendered <html lang="...">; it is not set from additional_head_code. Do not send Builder-only display fields such as schema_version, banner, header, general, sidebar, or main for HTML Mode. Scalev fills acceptable defaults internally. Responses can still include those fields. Include the analytics event fields even when they are empty:

{
  "render_mode": "html_mode",
  "html_code": "<main><h1>Launch offer</h1></main>",
  "css_code": "main { padding: 32px; }",
  "js_code": "",
  "additional_head_code": "<meta name=\"theme-color\" content=\"#09AFED\">",
  "csp_policy": {},
  "meta": {
    "lang": "id",
    "title": "Launch offer",
    "description": "A short offer description",
    "favicon": "https://cdn.example.com/favicon.ico",
    "thumbnail": "https://cdn.example.com/social-image.jpg",
    "isDisabledSearchEngineCrawler": false
  },
  "fb_pixel_ids": [],
  "tiktok_pixel_ids": [],
  "kwai_client_pixel_ids": [],
  "kwai_server_pixel_ids": [],
  "gtm_id": null,
  "onload_fb_events": [],
  "onload_tiktok_events": [],
  "onload_kwai_client_events": [],
  "onload_kwai_server_events": [],
  "fb_events_onload_parameters": {},
  "tiktok_events_onload_parameters": {},
  "kwai_client_events_onload_parameters": {},
  "kwai_server_events_onload_parameters": {}
}

html_code must not include <!doctype>, <html>, <head>, <body>, metadata, favicon tags, or domain settings. Put supported head tags in additional_head_code, and keep document-level convenience settings in meta. Use the HTML Mode runtime for checkout, analytics, prefill, and page context.

Analytics pixels and events

Attach existing analytics pixels to a page display by sending the Scalev pixel record IDs on the display payload. These are the numeric Scalev record IDs from GET /v3/fb-pixels, GET /v3/tiktok-pixels, and GET /v3/kwai-pixels, not the provider pixel code such as a Meta Pixel ID.

Field	Meaning
`fb_pixel_ids`	Scalev record IDs for Meta/Facebook pixels
`tiktok_pixel_ids`	Scalev record IDs for TikTok pixels
`kwai_client_pixel_ids`	Scalev record IDs for SnackVideo browser pixels
`kwai_server_pixel_ids`	Scalev record IDs for SnackVideo Events API pixels

Use POST /v3/fb-pixels, POST /v3/tiktok-pixels, POST /v3/kwai-pixels, and POST /v3/gtm when the business does not already have the record. Use GET /v3/gtm to find the gtm_id to send on the display payload. Only pixels owned by the same business are attached. IDs from another business or missing pixel records are ignored and will not appear in the response. Send an empty array when the new display should have no pixels for that provider. Configure automatic page-load events on the same page display:

{
  "fb_pixel_ids": [101],
  "tiktok_pixel_ids": [202],
  "kwai_client_pixel_ids": [303],
  "kwai_server_pixel_ids": [404],
  "gtm_id": 505,
  "onload_fb_events": ["PageView", "ViewContent"],
  "onload_tiktok_events": ["ViewContent"],
  "onload_kwai_client_events": ["contentView"],
  "onload_kwai_server_events": ["EVENT_CONTENT_VIEW"],
  "fb_events_onload_parameters": {
    "ViewContent": { "content_name": "Launch offer" }
  },
  "tiktok_events_onload_parameters": {},
  "kwai_client_events_onload_parameters": {},
  "kwai_server_events_onload_parameters": {}
}

HTML Checkout submit events are configured inside page_display.form_display, not on the top-level page display:

{
  "form_display": {
    "store_id": 123,
    "variant_ids": [456],
    "bundle_price_option_ids": [],
    "after_submit_event": "success_page",
    "onsubmit_fb_events": ["InitiateCheckout"],
    "onsubmit_tiktok_events": ["InitiateCheckout"],
    "onsubmit_kwai_client_events": ["formSubmit"],
    "onsubmit_kwai_server_events": ["EVENT_FORM_SUBMIT"],
    "fb_events_onsubmit_parameters": {},
    "tiktok_events_onsubmit_parameters": {},
    "kwai_client_events_onsubmit_parameters": {},
    "kwai_server_events_onsubmit_parameters": {}
  }
}

Read responses return full pixel objects under fb_pixels, tiktok_pixels, kwai_client_pixels, and kwai_server_pixels, not the ID arrays. When creating another display from a read response, use each pixel object’s id value in the matching *_pixel_ids request field.

Create an HTML Sales page

Omit form_display for a regular HTML landing page without checkout.

curl -X POST https://api.scalev.com/v3/pages \
  -H "Authorization: Bearer $SCALEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "API HTML Sales Page",
    "slug": "api-html-sales-page",
    "is_published": true,
    "page_display": {
      "render_mode": "html_mode",
      "html_code": "<main><h1>Launch offer</h1></main>",
      "css_code": "main { padding: 32px; }",
      "js_code": "",
      "csp_policy": {},
      "meta": { "lang": "id" },
      "fb_pixel_ids": [],
      "tiktok_pixel_ids": [],
      "kwai_client_pixel_ids": [],
      "kwai_server_pixel_ids": [],
      "gtm_id": null,
      "onload_fb_events": [],
      "onload_tiktok_events": [],
      "onload_kwai_client_events": [],
      "onload_kwai_server_events": [],
      "fb_events_onload_parameters": {},
      "tiktok_events_onload_parameters": {},
      "kwai_client_events_onload_parameters": {},
      "kwai_server_events_onload_parameters": {}
    }
  }'

The response returns the page directly, not inside the old data envelope.

Create an HTML Checkout page

Add page_display.form_display when the page should create orders. Checkout pages require:

store_id
at least one variant_ids item or one bundle_price_option_ids item

After a page has a saved store_id, every new display for that page must keep the same checkout store. A display with a different form_display.store_id, or a display without store context, is rejected.

{
  "name": "API HTML Checkout Page",
  "slug": "api-html-checkout-page",
  "is_published": true,
  "page_display": {
    "render_mode": "html_mode",
    "html_code": "<main><h1>Checkout offer</h1><button id=\"buy\">Buy now</button></main>",
    "css_code": "",
    "js_code": "",
    "csp_policy": {},
    "meta": { "lang": "id" },
    "fb_pixel_ids": [101],
    "tiktok_pixel_ids": [202],
    "kwai_client_pixel_ids": [303],
    "kwai_server_pixel_ids": [404],
    "gtm_id": 505,
    "onload_fb_events": [],
    "onload_tiktok_events": [],
    "onload_kwai_client_events": [],
    "onload_kwai_server_events": [],
    "fb_events_onload_parameters": {},
    "tiktok_events_onload_parameters": {},
    "kwai_client_events_onload_parameters": {},
    "kwai_server_events_onload_parameters": {},
    "form_display": {
      "store_id": 123,
      "variant_ids": [456],
      "bundle_price_option_ids": [],
      "after_submit_event": "success_page",
      "onsubmit_fb_events": ["InitiateCheckout"],
      "onsubmit_tiktok_events": ["InitiateCheckout"],
      "onsubmit_kwai_client_events": ["formSubmit"],
      "onsubmit_kwai_server_events": ["EVENT_FORM_SUBMIT"],
      "fb_events_onsubmit_parameters": {},
      "tiktok_events_onsubmit_parameters": {},
      "kwai_client_events_onsubmit_parameters": {},
      "kwai_server_events_onsubmit_parameters": {}
    }
  }
}

For checkout behavior after order creation, use these after_submit_event values:

Value	Required fields
`success_page`	None
`direct_to_whatsapp`	`handler_assignment`; if `handler_assignment` is `fixed`, also send `store_sales_person_id`
`direct_to_custom_whatsapp`	`custom_phone`
`other_page`	`other_page_id`
`custom_url`	`custom_url`
`is_sending_email_invoice`	None
`order_page`	None

Read HTML Mode checkout success paths for the runtime behavior of each path.

Update a page

PATCH /v3/pages/{page_id} updates page metadata and publish state.

{
  "name": "Updated page name",
  "slug": "updated-page-slug"
}

To publish a specific display:

{
  "is_published": true,
  "current_page_display_id": 987
}

To unpublish:

{
  "is_published": false,
  "current_page_display_id": null
}

Create and publish a new display

To change HTML, CSS, JavaScript, pixels, or checkout context, create a new page display: If the page already has a saved store, the new display must include the same form_display.store_id; omitting store context is rejected.

curl -X POST https://api.scalev.com/v3/pages/123/page-displays \
  -H "Authorization: Bearer $SCALEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "render_mode": "html_mode",
    "html_code": "<main><h1>New version</h1></main>",
    "css_code": "",
    "js_code": "",
    "csp_policy": {},
    "meta": { "lang": "id" },
    "fb_pixel_ids": [],
    "tiktok_pixel_ids": [],
    "kwai_client_pixel_ids": [],
    "kwai_server_pixel_ids": [],
    "gtm_id": null,
    "onload_fb_events": [],
    "onload_tiktok_events": [],
    "onload_kwai_client_events": [],
    "onload_kwai_server_events": [],
    "fb_events_onload_parameters": {},
    "tiktok_events_onload_parameters": {},
    "kwai_client_events_onload_parameters": {},
    "kwai_server_events_onload_parameters": {}
  }'

The response includes the new display id. Publish it with:

curl -X PATCH https://api.scalev.com/v3/pages/123 \
  -H "Authorization: Bearer $SCALEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "is_published": true,
    "current_page_display_id": 987
  }'

Tags and delete

Replace tags with:

{
  "tags": ["Promo", "Checkout"]
}

Call:

POST /v3/pages/{page_id}/update-tags

Delete a page with:

DELETE /v3/pages/{page_id}

Successful delete responses return 204 No Content.

​Auth

​Endpoints

​Complete setup flow

​HTML Mode display payload

​Analytics pixels and events

​Create an HTML Sales page

​Create an HTML Checkout page

​Update a page

​Create and publish a new display

​Tags and delete