Delete a PII Recognizer
Remove a custom recognizer.
DELETE
Delete a custom PII recognizer
Deletes the recognizer. Any policy that referenced it stops running that pattern
on the data plane within the recognizer cache’s short TTL — the cache is
invalidated on write, so it is effectively immediate.
Requires the
delete capability on ai_gateway. See the control-plane overview for authentication, the {data, meta} envelope, pagination and error types.Authorizations
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.