Skip to main content
DELETE
Delete Connector Endpoint
Deletion is asynchronous: the call returns 202 Accepted with an operation handle. Poll it like any other operation. By default, Ardent waits for in-progress replication to finish before deleting. Add ?force=true to skip that wait and abandon un-replicated changes. Two things block a delete: a deletion lock (409 — unlock it first) and, without force, replication that hasn’t finished yet.

Authorizations

Authorization
string
header
required

Ardent API key (sk-ard_live_… / sk-ard_test_…) or a dashboard session token.

Path Parameters

connector_id
string
required

Query Parameters

force
boolean
default:false

Response

Delete accepted (or already in progress). Poll GET /v1/operations/{operation_id}.

operation_id
string
required

Operation to poll at GET /v1/operations/{operation_id}.

resource_id
string | null
required

ID of the resource being created or acted on (the branch ID for branch create).

status
enum<string>
required

Status at acceptance time.

Available options:
pending,
running,
completed,
failed
type
enum<string>
required

The kind of work this operation tracks, for example branch_create.

Available options:
connector_engine_setup,
connector_reset,
connector_deep_reset,
connector_discovery,
connector_delete,
connector_secret_purge,
connector_rollout,
connector_replication_rollback,
connector_debezium_cutover,
connector_debezium_shadow_cleanup,
environment_deploy,
environment_destroy,
branch_create,
branch_delete