Update Redaction Config
Endpoints — Data redaction
Update redaction config
Replace the active CTR redaction config for your Operata account with a new allow-list or deny-list document.
PUT
Update Redaction Config
Replaces the redaction config for your Operata account with the body you send. It’s a full replace, not a patch — the document on disk after the call equals the document you sent. Use it to apply a new allow-list, switch from an allow-list to a deny-list, or extend the field set on an existing config.
The config is durable as soon as the call returns, but propagation across all collection points can take up to 30 minutes. CTRs from contacts that end before propagation completes may still apply the previous config.
Endpoint
Parameters
Headers
Body
The Cloud Collector always ships the mandatory CTR fields (for example
ContactId, InitiationTimestamp, Queue.Name) regardless of config. You cannot remove them with a deny-list or omit them from an allow-list.
PUT /v1/config/json is idempotent. Sending the same body twice yields the same final state — the document on disk after the second call equals the one on disk after the first. Retry safely. See Idempotency for the per-method contract across the API.
Response
200 OK with a plain-text body REDACTION_CONFIG updated.
Example
A deny-list that strips one PII attribute from every CTR:Errors
See Errors for shared codes such as
401 unauthorized, 429 rate_limited, and the 5xx family.
Related
- Data redaction — what redaction does and how the three endpoints fit together.
- Get redaction config — fetch the current config before you replace it.
- Delete redaction config — remove the config and revert to the default.
- Configure CTR redaction — the step-by-step rollout guide.
- Errors — shared status codes and recovery patterns.
- Rate limits — per-token request budget.
- Idempotency —
PUTis idempotent; sending the same body twice yields the same final state. - Versioning — this endpoint lives under
/v1.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Body
application/json
RAW_BODY
string<json>
default:{ "key": "REDACTION_CONFIG", "value": { "type":"BLACKLIST", "fields":[ "Attributes.CustomerDetails" ] } }
required
REDACTION_CONFIG object
Response
200