> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/requesting-a-cardholder-event-redaction.md).

# Requesting a Cardholder Event Redaction

### Introduction

This procedure describes how to send an active Cardholder Event Redaction request.

### Who is responsible

A Redaction REST API operator with the "Delete Cardholder History" operator privilege is responsible for requesting a Cardholder Event Redaction.

### Procedure

With the Cardholder ID, send a Cardholder Event Redaction request.

### Result

The request is received by the Cardholder API. If the request is successful, the following occurs:

* You receive a successful redaction request response.
* A 'Cardholder Event Redaction Requested' event is generated from the API call.
* Events relating to the Cardholder are redacted from the system at the scheduled time.
* A 'Cardholder Event Redaction Completed' event is generated at the scheduled time.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/pii-redaction/requesting-a-cardholder-event-redaction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
