---
title: "Delete Actions"
method: POST
path: "/actions/delete"
tags: ["Actions"]
---

# Delete Actions

`POST /actions/delete`

## Request

- Base URL: `https://api.peec.ai/customer/v1`
- URL: `https://api.peec.ai/customer/v1/actions/delete`
- Auth: one of:
  - API key in header `X-API-Key`
  - API key in query parameter `api_key`
  - HTTP bearer

Remove actions the customer wrote themselves. A generated action reads here exactly as a missing one does and lands in `skipped`: those are declined or dismissed through the status endpoint instead, so the list keeps a record of what Peec suggested and the customer turned down.

## Request body

- object
  - `project_id` string: Required if using a company api key
  - `action_ids` string[], required: Up to 50 action ids, from list_actions.

## Response `200`

Per-item results

- object: Per-item results
  - `deleted` object[], required
    - `action_id` string, required
  - `skipped` object[], required
    - `action_id` string, required
    - `reason` 'not_found', required

## Changes

- **2026-11-03** `9fdffdff48a5`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/peec/apis/peec-ai-customer-api/changes/actions/delete/post.md)

---

[API](https://skmtc.dev/peec/apis/peec-ai-customer-api.md) - [All operations](https://skmtc.dev/peec/apis/peec-ai-customer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/peec/apis/peec-ai-customer-api/revisions/9d774600c8eb?raw)