Skip to main content
DELETE
Delete Redaction Config
Removes the redaction config for your Operata account. After the call, the Cloud Collector reverts to the privacy-first default and ships only the mandatory CTR fields. Use it to roll back a config before applying a new one, or to retire a config you no longer need.
Destructive operation. Deleting the redaction config opens a propagation window during which subsequent CTRs may include PII fields the config previously stripped. The collector keeps applying the old config to in-flight contacts for up to 30 minutes after this call returns, then reverts to the default. To change the field set without this exposure window, send a new config to PUT /v1/config/json instead — that replaces the document atomically.
DELETE /v1/config/REDACTION_CONFIG is idempotent. Deleting an already-deleted config converges on the same end state — no config, collector on the default. The current wire response on a second call is 404 (see Errors below); treat it as success. See Idempotency for the per-method contract.

Endpoint

Parameters

Headers

This endpoint takes no path, query, or body parameters. Credentials on the request determine the Operata account scope.

Response

200 OK with a plain-text body REDACTION_CONFIG removed.
The deletion is durable as soon as the call returns. Propagation across all collection points can take up to 30 minutes; CTRs from contacts that end during that window may still apply the now-deleted config.

Example

Errors

See Errors for shared codes such as 401 unauthorized, 429 rate_limited, and the 5xx family.
  • Data redaction — what redaction does and how the three endpoints fit together.
  • Get redaction config — confirm what is in effect before you delete it.
  • Update redaction config — replace the config atomically instead of deleting then re-creating.
  • Errors — shared status codes and recovery patterns.
  • Rate limits — per-token request budget.
  • IdempotencyDELETE is idempotent; the end state matches whether the config existed or not.
  • Versioning — this endpoint lives under /v1.

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Response

200