# Delete sql

URL: https://docs.hanzo.ai/docs/openapi/provisioning/delete-provisioning-sql-by-name

> Deprovisions one Hanzo SQL database.

`DELETE /v1/provisioning/sql/{name}`

> [Provisioning →](https://docs.hanzo.ai/docs/openapi/provisioning) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                                   |
| ------------- | ------------------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/provisioning/sql/{name}` |
| **Method**    | `DELETE`                                          |
| **Operation** | `delete_provisioning_sql_by_name`                 |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`            |

Deprovisions one Hanzo SQL database. It reverts any app instance
bound to it back to Base BEFORE tearing down the org's dedicated Postgres
instance — never a live app pointed at a deleted backend — then deletes the
sealed credential and removes the metadata row. Answers 204 with no body; a
second call is a 404, not a second delete.

## Request

1 field.

| Field  | In   | Type   | Required | Description                                            |
| ------ | ---- | ------ | -------- | ------------------------------------------------------ |
| `name` | path | string | yes      | Name is the resource's org-unique slug, from the path. |

## Response

| Status    | Body            | Meaning    |
| --------- | --------------- | ---------- |
| `204`     | —               | no content |
| `default` | problem-details | refused    |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo provisioning sql rm <name>
```

**SDK**

**.ts**

```ts
import { Configuration, ProvisioningApi } from 'hanzoai';

const api = new ProvisioningApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteProvisioningSqlByName({ name: 'name' });
```

**.py**

```python
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProvisioningApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProvisioningApi(client).delete_provisioning_sql_by_name(name='name')
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProvisioningAPI.DeleteProvisioningSqlByName(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::apis::{configuration::Configuration, provisioning_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = provisioning_api::delete_provisioning_sql_by_name(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ProvisioningApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ProvisioningApi(client).deleteProvisioningSqlByName();
```

**HTTP**

```bash
curl -X DELETE https://api.hanzo.ai/v1/provisioning/sql/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **provisioning** through the `provisioning` tool, which names its 28 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_provisioning_datastore"
         }
       }
     }'
```

---

[Provisioning API](https://docs.hanzo.ai/docs/openapi/provisioning) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)