Skip to main content
The redaction config is a single JSON document stored against your Operata account. It tells the Cloud Collector which CTR (Contact Trace Record) fields to keep or drop before contact trace records leave AWS for Operata. One config per account. Three endpoints manage it.

Endpoints

Each endpoint is idempotent. See Idempotency for the per-method contract. PUT is a full replace — fields you omit from the new body do not survive the call.

Config shape

The config is one of two shapes, distinguished by value.type:
  • WHITELIST — allow-list. Ships only the mandatory CTR fields plus the fields you name.
  • BLACKLIST — deny-list. Ships every CTR field except the ones you name.
The mandatory CTR fields (for example ContactId, InitiationTimestamp, Queue.Name) ship regardless. A deny-list cannot remove them; an allow-list cannot omit them. With no config in place, the Cloud Collector applies the privacy-first default and ships only the mandatory CTR fields. The endpoints return 404 in that state.