Trigger Hunt
POST/api/v1/hunts/:name/run
Queue an ad-hoc run: mark the hunt due now for the runner to claim.
The pull model is kept. Nothing is pushed at the runner and no listener is added -- the fire is written into the coordination state, and the runner that is already running picks it up on its next poll, through the same claim that stops a hunt double-running. 202 says it is queued, not that it has run. The response carries the poll interval so the caller knows the longest wait before it starts.
A hunt with no rate schedule is not something the runner ticks, so a queued run for one sits unclaimed. That is the schedule's shape, not a failure here.
503 is reserved for ClickHouse actually being unreachable. Any other failure to write the request is a 500, so a bug here never reads as an outage.
Request
Responses
- 202
- 401
- 403
- 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
Validation Error
Problem details (RFC 9457)