Skip to main content
POST
Add a library question to an offering

Authorizations

Authorization
string
header
required

Per-client API key (M2M). Presented as Authorization: Bearer <key>.

Headers

Idempotency-Key
string

Optional. A unique key identifying this request, useful for tracing retries. Sending the same request again is never blocked — it creates another copy of the question and the response carries a duplicate-fact warning; remove an extra copy with the delete endpoint.

Path Parameters

offering_ref
string
required

Body

application/json
library_question_id
string
required

the id of the library question to copy onto the offering

Response

the offering-local copy of the question (a duplicate-fact warning may ride the body)

the saved question under data, plus non-blocking duplicate notices when another question already collects the same fact (the write still succeeds — warnings never block)

data
object
required

A client-authored screening question — a library definition or an offering-local copy. It binds a fact by its stable code (the code must resolve in your authoring fact catalog) and a display control, and carries your own wording. Copy and option labels are yours to author.

warnings
object[]