> For the complete documentation index, see [llms.txt](https://ask-clio.gitbook.io/ask-clio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/secure-client-confirmation-and-confirmed-action.md).
# Secure Client Confirmation & Confirmed Action
## Secure Client Confirmation & Confirmed Actions
Ask Clio supports Secure Client Confirmation for tools that take action on behalf of a client.
When Client Confirmation is enabled, Ask Clio prepares the proposed action, shows the client a confirmation modal with the inputs that will be sent, and only executes the API call after the client confirms.
This allows firms to safely support action-oriented workflows while keeping the final approval step with the client.
### Common use cases
Secure Client Confirmation can be used for workflows such as:
* Deposits and withdrawals
* Trading actions
* Account profile or address changes
* Operational account updates
* KYC or onboarding document collection
* Banking workflows that require client-provided documentation
* Other firm-defined actions that should require explicit client approval
### How it works
1. The firm creates or edits a tool from the Integrations tab.
2. The firm enables **Require client confirmation before executing**.
3. When the tool is triggered in chat, Ask Clio creates a draft of the action.
4. The client sees a confirmation modal in the SDK.
5. The client reviews the inputs that will be submitted.
6. After the client confirms, Ask Clio sends the request directly to the configured API.
### Why this matters
For sensitive workflows, the model should not directly execute an action without client approval. Client Confirmation creates a secure handoff between the conversational experience and the API execution step.
The model can help collect the required information, but the API call is only executed after the client confirms the final payload.
### File uploads and Client Confirmation
Tools that use the `file` Data Input type must have Client Confirmation enabled.
When a client uploads a file in the confirmation modal, the uploaded file is passed directly into the tool execution flow rather than being sent through the model.
---
# 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://ask-clio.gitbook.io/ask-clio/tools-and-data-plug-in-your-apis/secure-client-confirmation-and-confirmed-action.md?ask=&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.
