Fetch Redaction Config
Endpoints — Data redaction
Get redaction config
Fetch the active CTR redaction config for your Operata account so you can confirm what is in effect before changing it.
GET
Fetch Redaction Config
Fetches the redaction config currently in effect for your Operata account, as a single JSON document. Use it to confirm the active allow-list or deny-list before you replace or remove it. If no config exists, the endpoint returns
404 and the Cloud Collector falls back to the privacy-first default — it ships only the mandatory CTR fields.
Endpoint
Parameters
This endpoint takes no parameters. Credentials on the request determine the Operata account scope.Response
200 OK with the active redaction config.
Example
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.
- Update redaction config — replace the active config.
- Delete redaction config — remove the config and revert to the default.
- Errors — shared status codes and recovery patterns.
- Rate limits — per-token request budget.
- Idempotency —
GETis idempotent; retry without coordination. - Versioning — this endpoint lives under
/v1.