# Acknowledge a watch **POST /_watcher/watch/{watch_id}/_ack/{action_id}** **All methods and paths for this operation:**
PUT /_watcher/watch/{watch_id}/_ack
POST /_watcher/watch/{watch_id}/_ack
PUT /_watcher/watch/{watch_id}/_ack/{action_id}
POST /_watcher/watch/{watch_id}/_ack/{action_id}
Acknowledging a watch enables you to manually throttle the execution of the watch's actions. The acknowledgement state of an action is stored in the `status.actions..ack.state` structure. IMPORTANT: If the specified watch is currently being executed, this API will return an error The reason for this behavior is to prevent overwriting the watch status from a watch execution. Acknowledging an action throttles further executions of that action until its `ack.state` is reset to `awaits_successful_execution`. This happens when the condition of the watch is not met (the condition evaluates to false). To demonstrate how throttling works in practice and how it can be configured for individual actions within a watch, refer to External documentation. ## Required authorization * Cluster privileges: `manage_watcher` [Learn more about actions](https://www.elastic.co/docs/explore-analyze/alerts-cases/watcher/actions#example) ## Servers - http://api.example.com: http://api.example.com () ## Authentication methods - Api key auth - Basic auth - Bearer auth ## Parameters ### Path parameters - **watch_id** (string) The watch identifier. - **action_id** (string | array[string]) A comma-separated list of the action identifiers to acknowledge. If you omit this parameter, all of the actions of the watch are acknowledged. ## Responses ### 200 #### Body: application/json (object) - **status** (object) [Powered by Bump.sh](https://bump.sh)