Watch fire
A watch fire is one delivered change on a standing hiring search: the moment a company matching your criteria opens, changes or closes a requisition, and that change reaches your endpoint. It is the unit of monitoring — what is charged for is the change delivered, not the search kept open.
No fire, no charge. A watch bills when a change is delivered to you and your endpoint accepts it. A delivery that fails, or that repeats one you already received, is never charged for — metering runs after the acknowledgement, exactly once.
The distinction matters because the alternative — paying for the search rather than the result — makes monitoring most expensive exactly where it is least useful. A watchlist of two hundred accounts that have not hired all quarter should cost nothing; the same watchlist during a hiring surge should cost in proportion to the surge. Metering the fire rather than the watch is what lines the price up with the value.
A watch fire is also the smallest reportable event in a hiring-demand feed: it names the company, the requisition, and the moment the change happened. That makes it a record rather than a notification — something a CRM can store, a workflow can route on, and an audit can reconstruct after the fact.
See hiring-demand data for yourself
Query open requisitions by company, role and location — piped straight into your CRM or warehouse.
Get your free API key →Related terms
- → Req-level buying signal
- → Hiring-intent data
- → Ground-truth reqs
- → Competitive hiring intelligence
- → Hiring-demand API
- → Hiring-demand MCP
Part of the Reqbeat hiring-signal glossary.