Get an offering
Legacy — Offerings are superseded by Remote Configs; use Remote Configs for new integrations. Returns a single offering by ID.
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.
Response
Offering details.
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.