Delete Source
DELETE/api/v1/sources/:name
Delete a source by name. Its fetcher instance, receiver rule and topics go with it.
An engine-owned source -- the landing table's own -- is refused with 409
conflict, the same answer PUT and PATCH give.
The answer reports the reconcile as a create or an update does: on a
deployment that renders the app config itself, restart_required names the
command that takes away the containers the source's instances ran in.
A delete production+team sends to review answers review_required and
touches nothing else: main still carries the source, so its topics, records and
Search source stay until the branch is merged.
Request
Responses
- 200
- 401
- 403
- 409
- 422
- default
Successful Response
No valid session: the credentials are missing, invalid or expired, or the account behind them is disabled or blocked
Refused: the session lacks the action this route checks, or its account must replace an issued password first. A SCIM route answers a refused action in the RFC 7644 error envelope
The source is engine-owned and no write path may delete it
Validation Error
Problem details (RFC 9457)