---
search:
  tags:
    - servers
    - DELETE
seo:
  description: >-
    Deletes a server. Rejected with 409 while the server fills a member…
    Reference for the DELETE /api/v1/servers/{id} endpoint in the TimescaleDB
    Enterprise API.
  noindex: true
sidebar:
  label: Delete a server
  badge: DELETE
title: Delete a server
type: openapi-operation
---
Deletes a server. Rejected with 409 while the server fills a member slot of a database service or a DCS cluster (release it from its slot first), while a slot that it left is empty or waits for its rebuild (the rebuild needs its mesh address), while it hosts a LiveSync session, or while it hosts pgbackrest backup data; pass force=true to delete anyway with backup data (intended for dead or unreachable hosts): the stanza, repo, and binding rows referencing the server are removed and the on-disk backup data is abandoned. Without force, the console cleans a server first only when its recent reachability reading says that the server answers: the console stops and disables the database services on it and logs it out of the mesh. When such a server needs cleanup, the console runs the cleanup first, with the deletion of the PostgreSQL and etcd data of a slot that it left while unreachable: that runs as a workflow, the response is 202, and the console deletes the server when the workflow completes. A server that is unreachable, or that has no recent reachability reading, is deleted at once with 200, and the data on its disk stays.

`DELETE /api/v1/servers/{id}`

**Responses**

- `200` — OK
- `default` — Error

Response example, 200:

```json
{
  "deleted": true,
  "workflow_id": "string"
}
```
