Remove a knowledge source
Remove a knowledge source and the embedded chunks behind it. TAKES write_sales_agent:delete ON TOP OF write_sales_agent, and there is no reversible twin to offer instead. The row keeps a title and a chunk count and never the text, so the merchant’s own FAQ or policy wording is gone with it and the only copy left is wherever they wrote it originally. What that looks like afterwards is worse than an error: the assistant keeps answering, confidently, from whatever remains, and a shopper asking about the deleted returns policy gets the model’s guess instead of the merchant’s words. 204 on success. A source id this store does not own is a 404 rather than a silent 204, so a mistyped id cannot read as a removal that never happened.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Headers
A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.
Path Parameters
Response
Success. The response has no body.
