Atomically marks the offering as the project’s main offering
(tag = 1) and clears the previous main (tag = 0), inside a single
transaction. No request body required — the action target is fully
identified by the path parameter. Pass an Idempotency-Key header to
make retries safe (the same key replays the original response).
Experiment-variant offerings return 422 (typed code
cannot_setmain_experiment_variant).
Documentation Index
Fetch the complete documentation index at: https://documentation.qonversion.io/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication using the project Secret Key (prefixed with sk_, or test_sk_ for sandbox). All v4 public endpoints require the Secret Key — see Authentication. Never expose the Secret Key in client-side code.
64^[a-zA-Z0-9._:\- ]+$Offering marked as main.
offering 64^[a-zA-Z0-9._:\- ]+$"premium_monthly"
"/v4/offerings/premium_monthly"
Offering role within the project. 1 = main offering (TAG_MAIN)
— exactly one offering per project has tag=1 at any time; promote
via POST /v4/offerings/{offering_id}/set-main. 0 = regular
offering that was demoted from main. null = regular offering
that has never been tagged. Treat 0 and null as equivalent on
read. The Offerings endpoints filter out experiment-variant
offerings, but legacy rows could carry historical values other
than 0, 1, or null, so the response field is intentionally
not enum-restricted. Write schemas restrict accepted values
server-side.
Product UIDs that belong to this offering, in display order.
255^[a-zA-Z0-9._:\- ]+$"2025-09-15T12:30:00Z"
"2025-11-03T10:26:40Z"