# delete_site

Source: https://modulify.ai/docs/api/sites/delete-site

Permanently deletes a site and takes the live site offline.

- Title: Delete a site
- Scope: `sites:delete`
- Access: Destructive
- Endpoint: `POST /v1/delete_site`

It cannot be undone. The tool tells the client to confirm with you before calling it, and never to delete a site to tidy up on its own initiative. [Delete a project](https://modulify.ai/docs/projects/delete-and-restore#what-happens) lists everything that goes with it.

## Request

Call it with a `POST` to `https://api.modulify.ai/v1/delete_site`, sending the inputs below as a JSON object. The token needs the `sites:delete` scope.

> **Warning**
>
> This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an [Idempotency-Key](https://modulify.ai/docs/api/idempotency) header whenever you might retry it.

```bash
curl -X POST https://api.modulify.ai/v1/delete_site \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID"}'
```

Over MCP, the same method is the [delete_site tool](https://modulify.ai/docs/mcp/sites/delete-site).

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | Yes | The site to delete. |

## Response

Every call answers with the [JSON envelope](https://modulify.ai/docs/api/requests-and-responses#the-response) of `success`, `message`, `data`, `code` and `version`. `data` holds the result described above, and on a method that returns a total, `count` carries it. The [response headers](https://modulify.ai/docs/api/requests-and-responses#headers-on-every-method-call) carry the call's `X-Request-Id` and what is left of your per-minute budget in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`. [Errors](https://modulify.ai/docs/api/errors) explains every status code a call can answer with.