Contact Trace Records (CTR) collected by the Operata Conductor Lambda Function can contain sensitive data or personally identifiable information (PII). In some circumstances, it may be required to redact certain data before it is sent to Operata.
For Enterprise Customers, Operata has content redaction configuration that enables you to either Whitelist the CTR data that will be sent to Operata, or Blacklist of data not to be sent.
The lists are managed via the Operata API, It's secure and simple to use, just follow the steps below:
Setting up the Postman environment
Copy the Postman environment JSON file here and save as your own local JSON file using a tool of your choice.
Launch Postman, Select Environments and Import the JSON you have created.
Note: Ensure you have set the Postman Environment as the Active environment. [the tick Icon should be highlighted]
Now enter your Group ID and API key into both the INITIAL VALUE and CURRENT VALUE fields.
Where is my Group ID?
The URL shown when logged into the Operata Group, includes the Group ID, in the below example, it is the content that is highlighted in bold.
Where is the API token?
Here is the guide on how to find or create Operata API tokens.
Note: You will need to be an administrator to generate an API token.
Now enter your Group ID and API key into the INITIAL VALUE and then Save.
Importing the API collections
The Operata API supports a variety of functions, the collection we have created includes setting up Content Controls, here's how.
Copy the API v1 JSON file here and save as your own local JSON file using a tool of your choice.
Note: you will need to select the API v1 tab.
Launch Postman, Select Collections and Import the JSON you have created.
Importing the API v1 JSON will configure a group of API requests.
Use the redaction API's to set up Black or Whitelists that control the data sent to Operata, the guide below shows the detail.
If you have any issues, here's how to contact us.