Update customer PI settings
Replaces the customer’s prompt injection override as a whole. The override is sparse: set only the fields to pin, everything else inherits the organization policy. An empty body restores full inheritance. Changes propagate to request enforcement within about 60 seconds. Requires the customer_guardrails feature; without it the request is rejected with a 403.
Authentication
AuthorizationBearer
Your production key sent as a bearer token.
Path parameters
customer_id
Request
This endpoint expects an object.
pi_mode
Direct-injection enforcement mode: off, alert, or block
Allowed values:
pi_block_threshold
Direct-injection block threshold. Must be at least the organization’s pi_pass_threshold, which is not overridable per customer
pi_indirect_mode
Indirect-injection enforcement mode, a separate axis from pi_mode
Allowed values:
pi_tier2a_block_threshold
Indirect-injection heuristic-confidence threshold
pi_tier2b_block_threshold
Indirect-injection embedding-similarity threshold
pi_output_action
What to do when the response-side check fires
Allowed values:
pi_fail_closed
Whether to reject requests when the detection service is unavailable. Defaults to failing open
pi_allowlist_patterns
Regexes whose matching segments skip scanning. Unioned with the organization's list, never replacing it. A pattern broad enough to match ordinary prose disables enforcement rather than narrowing it
Response
Successful Response
override
What this customer sets. Fields it does not set are null here
effective
The policy a request scoped to this customer runs under
inherited_fields
Fields taken from the organization policy because the customer does not set them