Skip to main content
PATCH
Update a custom PII recognizer
Partial update. Omitted fields are left as they are. A new pattern is re-validated through the safe-regex compiler, so an update cannot install a pattern that a create would have refused. Requires the update capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.

Authorizations

Authorization
string
header
required

OAuth 2.1 authentication — recommended for new integrations. Access tokens (kc_ prefix) are minted at the root-host token endpoint https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>. Public clients must use PKCE with the authorization_code grant; confidential clients may use client_credentials. The first-party SDKs and the knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.

Path Parameters

id
string<uuid>
required

Body

application/json

Partial. The server validates the MERGED state, not the patch — pattern, kind and action together decide whether a pattern is compiled and how the detector is ranked.

name
string
kind
enum<string>
Available options:
regex,
aho_corasick,
presidio_pattern,
presidio_ner,
presidio_custom
pattern
string
context_words
string[]
confidence
number<float>
action
enum<string>
Available options:
redact,
tokenize,
whitelist,
warn
format
string | null
enabled
boolean

Response

The updated recognizer.

data
object

One tenant-defined PII detector.

meta
object

Metadata included with every API response.