Skip to main content
Screens are deprecated. The Screens product surface has been removed from the Qonversion dashboard. This API remains available for existing integrations only and should not be used for new development. No new Screens features are planned.
Screens are the no-code paywalls and onboarding flows built in the Qonversion dashboard or programmatically via the API. Each screen has a draft and a published version; users see the published version in the app.

​
Key concepts

  • Draft vs. published — Edits create a new draft; POST /v4/screens/{screen_id}/publish promotes it.
  • Context key — Screens are shown in the SDK via NoCodes.showScreen(contextKey).
  • Copy — POST /v4/screens/{screen_id}/copy duplicates a screen, useful when forking variants.
  • Analytics — Per-screen and overview analytics are available under /v4/screens/analytics/….
  • Summary vs. full payload — GET /v4/screens/{screen_id} returns the full V4Screen with render-time fields by default. Pass ?render=false to get the lean V4ScreenSummary (same shape as list rows) when you only need metadata and want to skip the render payload (configs, content, prod_key, sandbox_key, background, default_lang, used).

​
Available endpoints

​
Authentication

All v4 endpoints require a Secret Key. See Authentication.

​
Programmatic creation, dashboard editing

POST /v4/screens only takes a name. It creates an empty draft — the layout, media, components, and localisations are then built in the Qonversion dashboard’s no-code editor, which fills in configs, content, background, default_lang, prod_key, and sandbox_key over the life of the screen. Once a screen is published, the prod_key / sandbox_key values are what the Qonversion SDKs use at runtime.