# Delete cronjob of a web hosting package

> Delete one cronjob of a web hosting package.

- Effect: Destructive - Removes something for good. Agents ask first.
- Idempotent: no
- Stability: beta
- MCP tool: `manitu_webhosting_web_cronjob_delete` on https://mcp.manitu.de/mcp
- REST: `POST https://api.manitu.de/v1/webhosting/web/cronjob/delete`
- Needs: `service_webhosting`
- Page: /reference/webhosting/web/cronjob/delete/

**Removes something for good. Agents name what will be lost and wait for an explicit yes; a program should ask the same.**

## MCP tool

`manitu_webhosting_web_cronjob_delete`

### Description for the model

Deletes a cronjob of a web hosting package of the manitu customer account this connection works in, by site_id and cronjob_id from manitu_webhosting_web_cronjob_list. What it ran stays; its settings and run log are gone for good. To stop it for a while, use manitu_webhosting_web_cronjob_set with status inactive instead. Refused with a conflict when the package cannot be changed now (not_configurable). Ask the customer for an explicit yes first, naming what it runs and its description.

### Arguments

- `site_id` (integer | string, required) - The site_id from manitu_webhosting_list - never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)
- `cronjob_id` (integer | string, required) - The cronjob_id from manitu_webhosting_web_cronjob_list - never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)

### Example

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "manitu_webhosting_web_cronjob_delete",
    "arguments": {
      "site_id": 12345,
      "cronjob_id": 12345
    }
  }
}
```

## REST

`POST https://api.manitu.de/v1/webhosting/web/cronjob/delete`

### Authentication

One of `X-API-Key`, `Authorization: Bearer …` - never more than one in a request.

### Request body

JSON; unknown fields are refused.

- `site_id` (integer | string, required) - The site_id from manitu_webhosting_list - never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)
- `cronjob_id` (integer | string, required) - The cronjob_id from manitu_webhosting_web_cronjob_list - never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)

### Response

In `data`; the rest of the body as on every call.

- `cronjob_id` (integer, required) - The cronjob deleted.

### Statuses

- `200` Success.
- `400` The request does not match the declared input schema.
- `401` No credential was presented, or it was not recognised.
- `403` The credential is not permitted to use this operation.
- `500` The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.
- `503` The channel this operation forwards through is unavailable.

### Example

```sh
curl -X POST 'https://api.manitu.de/v1/webhosting/web/cronjob/delete' \
  -H 'X-API-Key: $API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"site_id":12345,"cronjob_id":12345}'
```

## Example result

```json
{
  "cronjob_id": 12345
}
```