Create an offering
Legacy — Offerings are superseded by Remote Configs; create Remote Configs for new integrations instead. Creates a new offering for the authenticated project. If the project has no offerings yet, the new one is auto-promoted to main (tag will be 1 in the response even if it was omitted in the request). Prefer POST /v4/offerings/{offering_id}/set-main over passing tag=1 here when switching the main of an existing project.
Authorizations
Bearer authentication using the project Secret Key (prefixed with sk_), used exactly as shown in the dashboard. Endpoints that support sandbox data take an explicit environment field or parameter. All v4 public endpoints require the Secret Key — see Authentication. Never expose the Secret Key in client-side code.
Body
Only 0 and null (or omitting the field) are accepted on create.
tag=1 is rejected with 400 cannot_set_main_directly — promote
via POST /v4/offerings/{offering_id}/set-main (atomic). The very
first offering in a project is auto-promoted to main even if tag
is omitted.
0, null Response
Offering created.
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.