---
title: "Clear your personal choice for a tool"
method: POST
path: "/v1/integrations/accounts/{account_id}/personal-tool-choices:clear"
tags: ["integrations"]
---

# Clear your personal choice for a tool

`POST /v1/integrations/accounts/{account_id}/personal-tool-choices:clear`

## Request

- Base URL: `https://api.patricia.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.patricia.app/v1/integrations/accounts/{account_id}/personal-tool-choices:clear`
- Auth: HTTP bearer

Delete the calling member's own Ask/Never-Allow choice for one tool, returning it to "following your default". A personal Always-Allow choice is separate from a per-tool integration consent. General policy still cannot clear a CRITICAL tier, a mandatory call, a managed account, or the workspace master switch. Idempotent: clearing an already-clear choice is a no-op, never an error.

## Path parameters

- `account_id` string, uuid, required

## Headers

- `X-Tenant-Id` string, nullable

## Request body

- PersonalToolChoiceClearRequest
  - `tool_ref` string, required

## Response `204`

Successful Response

## Other responses

- `400`: Bad request
- `401`: Unauthorized
- `403`: Forbidden. Inspect response body `code` for the specific reason (for example: PERMISSION_DENIED, EMAIL_NOT_VERIFIED, TENANT_ACCESS_REQUIRED, ROLE_UNRESOLVED)
- `404`: Not found
- `409`: Conflict
- `422`: Validation error

---

[API](https://skmtc.dev/patricia/apis/patricia-api.md) · [All operations](https://skmtc.dev/patricia/apis/patricia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/patricia/apis/patricia-api/revisions/0dfb44495ea1?raw)