Delete a capture connector at an expected revision
DELETE/api/v1/capture/connectors/:connector_id
Requires connectors.manage, same-origin checks for cookie requests, and the current expectedRevision; stale revisions return 409.
Request
Responses
- 204
- 400
- 401
- 403
- 404
- 409
- 421
- 503
Connector deleted at the supplied revision
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request syntax, headers, body, or validated input is malformed or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The resource is unknown or outside the authenticated household scope
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request conflicts with the current resource, revision, lease, credential, or idempotency state
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A required core dependency is unavailable; retry with bounded backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.