Deprecate version
Marks a version deprecated — a non-destructive marker. Requires the admin:schemas:write scope. Rulesets bound to the version keep evaluating and their traffic is accepted while an operational signal flags it; creating a ruleset bound to a deprecated version rejects, and activating a ruleset whose binding became deprecated rejects. Versions are never auto-removed; there is no hard-removal flow. Deprecating a built-in schema or an already-deprecated version is an invalid transition.
Authorizations
HS256-signed JWT bearer token, obtained via the OAuth2 client-credentials grant (see Authentication).
Path Parameters
Schema name
Schema version (system-assigned integer)
Response
Deprecated version
Whether velocity counters carry over from the previous version for field paths present in both versions. When false, rulesets bound to this version count from zero — counters of earlier versions are untouched and keep serving the rulesets bound to them. Blacklist entries are not versioned — they are global and unaffected by this flag. Fixed at publication and immutable thereafter. Always true for version 1.
Null for version 1 of a built-in schema, which ships with the platform.
The JSON Schema document. Each field carries x-specter-type (one of the 23 entries of the type vocabulary — string, integer, number, boolean, email, iban, country-code, currency-code, language-code, date, datetime, url, uuid, phone, ip, amount, pan, masked-pan, scheme-enum, card-funding-type-enum, card-segment-enum, object, array) and optionally x-data-classification (any — the default — pii, pci-pan, pci-sad). A pan field is always pci-pan; masked-pan defaults to pii. Types validate the decision payload at ingestion; markers drive the PCI gate, redaction, and retention. See Schemas.
"customer-registration"
active, deprecated System-assigned monotonic integer per schema, starting at 1. Merchants never choose it.
2