---
title: "Lock Connector Deletion Endpoint"
method: POST
path: "/v1/connectors/{connector_id}/deletion-lock"
tags: ["v1-connectors"]
---

# Lock Connector Deletion Endpoint

`POST /v1/connectors/{connector_id}/deletion-lock`

Lock connector deletion until an authorized caller unlocks it.

## Path parameters

- `connector_id` string, required

## Request body

- ConnectorDeletionLockRequest
  - `reason` string, nullable — Why the connector is locked, up to 500 characters.

## Response `200`

The locked connector.

- ConnectorEnvelope — Spec-only wrapper used by the deletion-lock endpoints.
  - `connector` ConnectorRow, required — Loose core of a connector response. The connector row is the most dynamic shape in the system; extra="allow" is the contract — responses carry many more columns and clients must tolerate fields not listed here. can_update/can_delete are added by the permission projection on create/get/update/list responses.
    - `id` string, required — Connector ID.
    - `org_id` string, required — Organization the connector belongs to.
    - `project_id` string, nullable — Project the connector belongs to.
    - `name` string, required — Connector name.
    - `service_name` string, required — Service type. `postgresql` today.
    - `status` string, nullable — Current connector status.
    - `created_at` string, nullable — When the connector was created.
    - `can_update` boolean, nullable — Whether the caller may update this connector.
    - `can_delete` boolean, nullable — Whether the caller may delete this connector.

## Other responses

- `403` — No update permission on this connector.
- `404` — Connector not found (or not visible to the caller).
- `409` — A delete is already in progress.
- `422` — Validation Error

---

[API](https://skmtc.net/tryardent/apis/fastapi.md) · [All operations](https://skmtc.net/tryardent/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tryardent/fastapi/versions/f92d8d54bae2/schema)
