---
title: "deleteQueryTemplate"
description: "Delete a query template"
canonical: "https://pgbeam.com/docs/ts-sdk/policies/deleteQueryTemplate"
last-updated: "2026-10-20T10:24:51.000Z"
---

# deleteQueryTemplate

> Delete a query template

URL: https://pgbeam.com/docs/ts-sdk/policies/deleteQueryTemplate

{/* Auto-generated from OpenAPI. Do not edit. Run `pnpm generate:sdk-docs` to regenerate. */}

Removes the template, so a profile that runs templates only stops admitting its statement. Deleting the last template is allowed: such a profile then admits nothing, which is the intended way to withdraw access in an incident.

## Usage

```typescript
const result = await api.policies.deleteQueryTemplate({
  pathParams: { project_id: "prj_xxx", query_template_id: "qtp_xxx" },
});
```

## Parameters

| Parameter                    | Type     | Required | Description                                                |
| ---------------------------- | -------- | -------- | ---------------------------------------------------------- |
| pathParams.project_id        | `string` | Yes      | Unique project identifier (prefixed, e.g. prj_xxx).        |
| pathParams.query_template_id | `string` | Yes      | Unique query template identifier (prefixed, e.g. qtp_xxx). |

## Response

`Promise<void>`: no content.

## Example

```typescript
import { PgBeamClient } from "pgbeam";

const client = new PgBeamClient({
  token: "pbu_...",
  baseUrl: "https://api.pgbeam.com",
});

const result = await client.api.policies.deleteQueryTemplate({
  pathParams: { project_id: "prj_xxx", query_template_id: "qtp_xxx" },
});
```

## Errors

| Status | Description                                                                                                                                                                                                                                                                                           |
| ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 400    | The request was rejected. `code` is `INVALID_INPUT`, and `errors` names the offending fields when the failure was a validation one.                                                                                                                                                                   |
| 401    | Missing or invalid authentication. `code` is `UNAUTHORIZED`.                                                                                                                                                                                                                                          |
| 403    | The caller is authenticated but not allowed to perform this operation. `code` is `FORBIDDEN` when the caller's role is insufficient, and `PLAN_LIMIT_REACHED` when the organization's plan is what stands in the way. The two are answered differently, so branch on the code rather than the status. |
| 404    | The resource does not exist, or the caller is not entitled to know that it does. `code` is `NOT_FOUND`.                                                                                                                                                                                               |
| 500    | The request failed for a reason on our side. `code` is `INTERNAL_ERROR`. Quote `request_id` when reporting it.                                                                                                                                                                                        |