---
title: "Delete a document in a table"
method: POST
path: "/delete"
tags: ["Index"]
---

# Delete a document in a table

`POST /delete`

Delete one or several documents.
The method has 2 ways of deleting: either by id, in case only one document is deleted or by using a  match query, in which case multiple documents can be delete .
Example of input to delete by id:

  ```
  {'table':'movies','id':100}
  ```

Example of input to delete using a query:

  ```
  {
    'table':'movies',
    'query':
    {
      'bool':
      {
        'must':
        [
          {'query_string':'new movie'}
        ]
      }
    }
  }
  ```

The match query has same syntax as in for searching.
Responds with an object telling how many documents got deleted: 

  ```
  {'table':'products','updated':1}
  ```

## Request body

- DeleteDocumentRequest — Payload for delete request. Documents can be deleted either one by one by specifying the document id or by providing a query object. For more information see [Delete API](https://manual.manticoresearch.com/Deleting_documents)
  - `table` string, required — Table name
  - `cluster` string — Cluster name
  - `id` integer
  - `query` object — Defines the criteria to match documents for deletion

## Response `200`

item updated

- DeleteResponse — Response object for successful delete request
  - `table` string — The name of the table from which the document was deleted
  - `deleted` integer — Number of documents deleted
  - `id` integer
  - `found` boolean — Indicates whether any documents to be deleted were found
  - `result` string — Result of the delete operation, typically 'deleted'

## Other responses

- `default` — error

## Changes

- **2026-08-04** `eb39c8083035` — 3 breaking, 1 info
  - added `#/components/schemas/documentId` to the `id` request property `allOf` list
  - the `id` request property type/format changed from `integer`/`uint64` to ``/``
  - the `id` response's property type/format changed from `integer`/`uint64` to ``/`` for status `200`
  - added `#/components/schemas/documentId` to the `id` response property `allOf` list for the response status `200`
- **2025-06-30** `1911b776f18a` — 2 breaking
  - the `id` request property type/format changed from `integer`/`int64` to `integer`/`uint64`
  - the `id` response's property type/format changed from `integer`/`int64` to `integer`/`uint64` for status `200`
- **2025-04-01** `0e6cccea382d` — 1 warning, 1 info
  - removed the optional property `_id` from the response with the `200` status
  - added the optional property `id` to the response with the `200` status
- **2025-02-13** `8f90aac993c7` — 1 breaking, 3 warning, 2 info
  - added the new required request property `table`
  - removed the request property `index`
  - removed the optional property `_index` from the response with the `200` status
  - removed the optional property `error/oneOf[#/components/schemas/responseErrorDetails]/index` from the response with the `default` status
  - …2 more
- …earlier changes not shown

[Full history](https://skmtc.dev/manticoresoftware/apis/manticore-search-client/changes/delete/post.md)

---

[API](https://skmtc.dev/manticoresoftware/apis/manticore-search-client.md) · [All operations](https://skmtc.dev/manticoresoftware/apis/manticore-search-client/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/manticoresoftware/manticore-search-client/revisions/eb39c8083035/schema)
