Unmark for anonymization
- 25 Jan 2022
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Unmark for anonymization
- Updated on 25 Jan 2022
- 1 Minute to read
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
PUT /external/schedule/{externalId}/anonymize/unmark
The {externalId} in the URL is the external id of schedule that has been marked for anonymization but not anonymized yet.
If a schedule has been Marked for anonymization you are still able to undo this as long as the Anonymization Notice Period has not transpired yet as the schedule may not have been anonymized yet.
Request
Always include the required HTTP Headers
Apart from {externalId} in the URL no other parameters or body.
Sample Request URL
https://api.cirrusplatform.com/api/v1/integrations/external/schedule/EXT_sch_1/anonymize/unmark
Response codes
| Code | Description |
|---|---|
| 200 | Successful operation |
| 321 | Anonymization not supported |
| 326 | Schedule has already been anonymized |
| 327 | Schedule not marked for anonymization |
| 403 | Not allowed to use external API |
| 500 | Internal server error |
Was this article helpful?