three_ up_ hours
Three consecutive higher hourly closes.
Facts
A boolean signal: screen on it by its bare name (three_up_hours, or NOT three_up_hours). It's null on tickers it doesn't apply to.
| definition | close > close_1h_ago > close_2h_ago > close_3h_ago |
| type | state (boolean) |
| firing | continuous |
| refresh | 1 min · 4 AM–8 PM ET · crypto and FX 24/7 |
| asset classes | US equities, Crypto, FX |
| coverage | all tickers |
| history | live value only |
Examples
Screen on it
curl -X POST "https://api.tickerbot.io/v2/scan" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"q": "three_up_hours"
}'Get an alert when a ticker starts matching
curl -X POST "https://api.tickerbot.io/v2/scan/subscribe" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"q": "three_up_hours",
"target_url": "https://example.com/hooks/tickerbot"
}'Returns 201 with the created webhook object; deliveries carry the tickers matching the condition at each evaluation.
Its firings
curl -G "https://api.tickerbot.io/v2/events" \
-d "kind=signal" -d "from=2026-04-09" -d "signal=three_up_hours" -d "transition=enter" \
-H "Authorization: Bearer YOUR_KEY"