Create a new catalog ruleset version

Persists a ruleset under the declared name@version. Existing name@version combinations are rejected with 409 — rulesets are immutable once stored. Omitting version auto-assigns the next integer under that name (1 if no prior version exists).

POST /v1/rulesets

Create a new catalog ruleset version

cURL

curl --request POST \
  --url https://api.example.com/v1/rulesets \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "checks": [
    {}
  ],
  "name": "<string>",
  "sets": {},
  "verdict_policy": {},
  "version": 123
}
'

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

checks · Checks · object[] · required

name · string · required

sets · Sets · object · required

verdict_policy · Verdict Policy · object

version · integer | null

Response

201

application/json

Successful Response