Delete a keyword
Stops monitoring and removes the keyword. Feeds whose filters reference only this keyword are deleted too, and each of those feeds takes its notification with it. The response names both: deletedFeeds and deletedNotifications are always present, and empty when nothing else was destroyed. Use GET /api/v2/keywords/{id}/deletion-preview to see the same cascade before committing to it.
Authorizations
Clerk API key. Create one in Settings → API Keys. Pass as Authorization: Bearer <key>. Keys carry a scope — read, write (implies read) or admin (implies write) — chosen when the key is minted. Each operation's security requirement (and its x-required-scope extension) names the minimum scope it needs; request the least-privileged key that covers the operations you call.
Path Parameters
-9007199254740991 <= x <= 9007199254740991Response
200 response
The keyword was deleted. deletedFeeds/deletedNotifications name the cascade — always present, empty when nothing else was destroyed.
Feeds destroyed alongside the keyword, because their filters referenced only it. Empty when nothing cascaded.
Notifications destroyed alongside those feeds. Empty when nothing cascaded. A notification cannot outlive the feed it is attached to, so this is a strict consequence of deletedFeeds.
