Skip to main content
PATCH
Update ruleset

Authorizations

Authorization
string
header
required

HS256-signed JWT bearer token, obtained via the OAuth2 client-credentials grant (see Authentication).

Path Parameters

id
string
required

Ruleset ID

Body

application/json

Update attributes

Only DRAFT rulesets are editable. Omit a field to leave it unchanged. The identity fields context and schema are not updatable — a request carrying a changed value rejects with 422 naming the field, while carrying the current value unchanged is a no-op, so read-modify-write clients may echo the full object back.

description
string
Example:

"Block USD transactions over limit"

rules
RuleInput · object[]

Replaces the full rules array

Response

Updated ruleset

id
string<uuid>
Example:

"6c1f4e8b-9a2d-4c7e-b5f3-8d1a6e9c4b2f"

activated_at
string<date-time> | null
Example:

"2026-05-15T08:00:00Z"

context
string
Example:

"checkout"

created_at
string<date-time>
Example:

"2026-05-14T16:20:00Z"

created_by
string | null
Example:

"ops@example.com"

description
string | null
Example:

"Block USD transactions over limit"

rules
Rule · object[]

Rule definitions evaluated in array order

schema
SchemaBinding · object

A ruleset's declared (schema, version) pair. name references a registry entry; version is required for custom schemas and absent for built-ins, whose version is implicit and advances only via Specter releases. Set at ruleset creation and immutable for the life of that ruleset version — rebinding a context means publishing a new ruleset version with the new binding and activating it. Rulesets that predate the registry surface the launch-backfilled transaction binding.

status
enum<string>
Available options:
DRAFT,
ACTIVE,
INACTIVE
version
integer
Example:

1