Mark a single signal as dismissed so it stops appearing in the feed. Idempotent.
PATCH /api/v1/signals/types/{id} with enabled: false.
The row itself is preserved; historical queries with explicit since/until filters can still surface dismissed signals if needed (for audit or re-evaluation workflows).
{ success: true }. Safe to retry on network errors.Typical flow. Agent reads the feed, presents the top signals to the human, human marks one as not relevant, agent calls dismiss. Or: agent has its own scoring model, filters signals with confidence below a threshold, and dismisses them.Feedback is separate. /dismiss hides the signal; /feedback (positive/negative) trains the scoring model. If the signal is low-quality AND you want to train against it, call both — dismiss first, then submit negative feedback.This is the public partner API — rate-limited at 100 req/min. Use this rather than the internal /api/signals/feed/{id}/dismiss endpoint.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Signal UUID.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Signal dismissed.
true