Skip to main content
POST
Apply a setup proposal

Authorizations

Authorization
string
header
required

Clerk API key. Create one in Settings → API Keys. Pass as Authorization: Bearer <key>. Keys carry a scope — read, write (implies read) or admin (implies write) — chosen when the key is minted. Each operation's security requirement (and its x-required-scope extension) names the minimum scope it needs; request the least-privileged key that covers the operations you call.

Path Parameters

id
string
required

The setup draft id (draft_…) or the proposal id it carries.

Required string length: 1 - 191
Example:

"draft_x2Yk9…"

Body

application/json
selections
object

What the user kept. Omitted = every keyword selected by default.

Response

200 response

What apply created: one keyword per kept proposal keyword with only its quiet settings, and the workspace platforms. Idempotent — a re-run returns the same ids.

draftId
string
required
proposalId
string
required
organizationId
string
required
appliedAt
string
required
keywords
object[]
required
platforms
object
required
quietSettings
string[]
required
flags
string[]
required
reviewSummary
string[]
required