---
title: "KMS Config Delete"
method: DELETE
path: "/1/kms/configs/{kmsConfigId}"
tags: ["KMS Configuration"]
---

# KMS Config Delete

`DELETE /1/kms/configs/{kmsConfigId}`

## Request

- Base URL: `http://localhost:3000/api`
- URL: `http://localhost:3000/api/1/kms/configs/{kmsConfigId}`
- Auth: API key in header `Authorization`
- TypeScript: <https://skmtc.dev/ironcorelabs/apis/vendor-api-bridge/docs/1/kms/configs/:kmsConfigId/delete.ts> (a function with typed inputs; its response is checked against the schema)

Delete the specified KMS configuration. In order to succeed, the configuration must be owned by the calling vendor and not have any tenant assignments.

This API allows for destructively offboarding a tenant with active secrets. Secrets are not recoverable and any downstream services (Deterministic Encryption, Cloaked Search) will fail when attempting to do things with those secrets. **We strongly advise checking for `secret_count == 0` before issuing a KMS Configuration DELETE**.

## Headers

- `icl-requestor-id` string, required

## Response `200`

Result of deleting a KMS configuration

- object
  - `id` integer, required: KMS configuration ID

## Other responses

- `401`: Unauthorized
- `422`: Unprocessable Entity Possible causes: \- Invalid KMS configuration ID provided \- Kms configuration not owned by calling vendor \- Config currently in use via an assignment

---

[API](https://skmtc.dev/ironcorelabs/apis/vendor-api-bridge.md) - [All operations](https://skmtc.dev/ironcorelabs/apis/vendor-api-bridge/llms.txt) - [OpenAPI document](https://skmtc.dev/ironcorelabs/apis/vendor-api-bridge/revisions/5c0e553ffa21?raw)