---
title: "Disable Destination"
method: POST
path: "/pci-proxy/destinations/{id}/disable"
---

# Disable Destination

`POST /pci-proxy/destinations/{id}/disable`

Turns a destination off without removing it — the record and its audit history are kept, but the forward path rejects it with `403 DESTINATION_NOT_ALLOWED` until it is enabled again.

## Path parameters

- `id` string, uuid, required

## Response `200`

The destination was disabled; the updated object is returned.

- Destination
  - `id` string, uuid — Unique identifier of the destination. Use it to remove the destination.
  - `account_id` string, nullable — The account this destination is scoped to, or `null` when it applies to the whole organization.
  - `hostname` string — The registered hostname.
  - `status` 'ENABLED' | 'DISABLED' — Whether the destination is active. Only ENABLED destinations are used by the forward path.
  - `purpose` string — The label you provided when registering the destination.
  - `created_at` string, date-time — When the destination was registered.
  - `updated_at` string, date-time — When the destination was last changed.

## Other responses

- `400` — The `id` path parameter is not a valid UUID.
- `401` — Your API credentials are missing or invalid.
- `404` — No destination with that `id` is registered for your scope.

---

[API](https://skmtc.net/y/apis/ai-caller.md) · [All operations](https://skmtc.net/y/apis/ai-caller/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/y/ai-caller/revisions/05b629819b49/schema)