> ## Documentation Index
> Fetch the complete documentation index at: https://docs.operata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get redaction config

> Fetch the active CTR redaction config for your Operata account so you can confirm what is in effect before changing it.

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

```http theme={null}
GET https://api.operata.io/v1/config/REDACTION_CONFIG/json
```

## Parameters

This endpoint takes no parameters. Credentials on the request determine the Operata account scope.

## Response

`200 OK` with the active redaction config.

```json theme={null}
{
  "key": "REDACTION_CONFIG",
  "value": {
    "type": "BLACKLIST",
    "fields": [
      "Agent.ARN",
      "Agent.RoutingProfile"
    ]
  }
}
```

| Field          | Type            | Description                                                                                                                                                             |
| -------------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `key`          | string          | Always `REDACTION_CONFIG`. Identifies the config record.                                                                                                                |
| `value`        | object          | The redaction config body.                                                                                                                                              |
| `value.type`   | string          | `WHITELIST` for an allow-list, `BLACKLIST` for a deny-list. One config per account; the two modes are mutually exclusive.                                               |
| `value.fields` | array of string | The CTR field paths to include (allow-list) or exclude (deny-list). Dot notation matches the CTR data model — see [Contact trace records](/docs/contact-trace-records). |

## Example

<CodeGroup>
  ```bash curl theme={null}
  curl -u "$OPERATA_GROUP_ID:$OPERATA_API_TOKEN" \
    "https://api.operata.io/v1/config/REDACTION_CONFIG/json"
  ```

  ```javascript Node.js theme={null}
  const groupId = process.env.OPERATA_GROUP_ID;
  const apiToken = process.env.OPERATA_API_TOKEN;
  const auth = Buffer.from(`${groupId}:${apiToken}`).toString("base64");

  const response = await fetch(
    "https://api.operata.io/v1/config/REDACTION_CONFIG/json",
    { headers: { Authorization: `Basic ${auth}` } },
  );
  const config = await response.json();
  ```

  ```python Python theme={null}
  import os, requests

  response = requests.get(
      "https://api.operata.io/v1/config/REDACTION_CONFIG/json",
      auth=(os.environ["OPERATA_GROUP_ID"], os.environ["OPERATA_API_TOKEN"]),
  )
  response.raise_for_status()
  config = response.json()
  ```
</CodeGroup>

## Errors

| Status | Code        | When                                                                                                              | Recover                                                                                                                |
| ------ | ----------- | ----------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| 404    | `not_found` | No redaction config exists for this Operata account. The Cloud Collector falls back to the privacy-first default. | Create a config with [Update redaction config](/docs/api-update-redaction-config) if you want to override the default. |

See [Errors](/docs/api-errors) for shared codes such as `401 unauthorized`, `429 rate_limited`, and the `5xx` family.

## Related

* [Data redaction](/docs/api-data-redaction) — what redaction does and how the three endpoints fit together.
* [Update redaction config](/docs/api-update-redaction-config) — replace the active config.
* [Delete redaction config](/docs/api-delete-redaction-config) — remove the config and revert to the default.
* [Errors](/docs/api-errors) — shared status codes and recovery patterns.
* [Rate limits](/docs/api-rate-limits) — per-token request budget.
* [Idempotency](/docs/api-idempotency) — `GET` is idempotent; retry without coordination.
* [Versioning](/docs/api-versioning) — this endpoint lives under `/v1`.


## OpenAPI

````yaml GET /v1/config/REDACTION_CONFIG/json
openapi: 3.0.3
info:
  title: operata-api
  version: '1'
servers:
  - url: https://api.operata.io/
security:
  - sec0: []
paths:
  /v1/config/REDACTION_CONFIG/json:
    get:
      summary: Fetch Redaction Config
      description: Retrieve the CTR redaction configuration
      operationId: fetch-redaction-configuration
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                Result:
                  value: |-
                    {
                        "key": "REDACTION_CONFIG",
                        "value": {
                            "type": "BLACKLIST",
                            "fields": [
                                "Agent.ARN",
                                "Agent.RoutingProfile"
                            ]
                        }
                    }
              schema:
                type: object
                properties:
                  key:
                    type: string
                    example: REDACTION_CONFIG
                  value:
                    type: object
                    properties:
                      type:
                        type: string
                        example: BLACKLIST
                      fields:
                        type: array
                        items:
                          type: string
                          example: Agent.ARN
        '404':
          description: '404'
          content:
            text/plain:
              examples:
                Result:
                  value: REDACTION_CONFIG not found
      deprecated: false
components:
  securitySchemes:
    sec0:
      type: http
      scheme: basic

````