Skip to main content
POST
Create a draft version from a rule table

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

workspace
string
required

Workspace slug.

Maximum string length: 64
Pattern: ^[a-z0-9][a-z0-9-]{0,63}$
key
string
required

Decision key — a flat slug, never a path.

Maximum string length: 64
Pattern: ^[a-z0-9][a-z0-9-]{0,63}$

Body

application/json

Author a version from a rule table rather than from raw JDM.

spec
Spec · object
required

The rule table: inputs, outputs, hit_policy and rules. Compiled to JDM server-side — the graph is never accepted directly from this path.

notes
string | null

What changed and why.

Response

Successful Response

workspace
string
required
key
string
required
version
integer
required
content_sha
string
required
status
enum<string>
required

Lifecycle state of a single version.

draft → submitted → approved, with reject returning a submitted version to draft and retire taking an approved version out of circulation.

Available options:
draft,
submitted,
approved,
retired
created_by
string
required
created_at
string<date-time>
required
content
string
required

Raw JDM JSON, byte-exact.

notes
string | null
submitted_by
string | null
submitted_at
string<date-time> | null
approved_by
string | null
approved_at
string<date-time> | null
source_instance
string | null
source_version
integer | null
edited_in_place
boolean
default:false

True when an existing draft was rewritten rather than a new version added.