← tickerbot.io
View as markdown

three_up_hours

Three consecutive higher hourly closes.

definition
close > close_1h_ago > close_2h_ago > close_3h_ago

Swap YOUR_KEY for a key from /dashboard/keys. Responses are real captures from 2026-09-18, trimmed.

Every ticker matching this signal /v2/signals/{signal}

Live — every ticker where it fires now
curl "https://api.tickerbot.io/v2/signals/three_up_hours" \
  -H "Authorization: Bearer YOUR_KEY"
Response (sampled 2026-09-18, trimmed)
{
 "as_of": "2026-09-18T14:42:22.811Z",
 "signal": "three_up_hours",
 "condition": null,
 "universe": null,
 "count": 0,
 "results": []
}
Subscribe — webhook when a ticker starts matching
curl -X POST "https://api.tickerbot.io/v2/signals/three_up_hours/subscribe" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_KEY" \
  -d '{"target_url": "https://example.com/hooks/tickerbot"}'

Returns 201 with the created webhook — the same shape as GET /v2/webhooks/{id}, plus a one-time signing_secret for HMAC verification.

The whole market, filtered on it /v2/scan

Live — the whole market, filtered on this signal
curl -X POST "https://api.tickerbot.io/v2/scan" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_KEY" \
  -d '{ "q": "three_up_hours" }'
Response (sampled 2026-09-18, trimmed)
{
 "as_of": "2026-09-18T14:42:23.521Z",
 "query": {
  "q": "three_up_hours",
  "limit": 2,
  "order": "change_1d_pct",
  "dir": "desc",
  "fields": [],
  "full": false,
  "universe": null,
  "asset_class": null
 },
 "count": 0,
 "results": []
}
Subscribe — webhook on a market-wide condition
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 /v2/events

Firings — every enter edge as a point event
curl -G "https://api.tickerbot.io/v2/events" \
  -d "kind=signal" -d "signal=three_up_hours" -d "transition=enter" -d "from=2026-02-24" \
  -H "Authorization: Bearer YOUR_KEY"
Response (sampled 2026-09-18, trimmed)
{
 "as_of": "2026-09-18T14:42:23.701Z",
 "query": {
  "kind": "signal",
  "tickers": null,
  "universe": null,
  "since": "2026-02-10T00:00:00.000Z",
  "until": null,
  "limit": 2,
  "signal": "three_up_hours",
  "transition": "enter"
 },
 "count": 2,
 "results": [
  {
   "ticker": "LIEN",
   "ts": "2026-09-17T21:12:40.182Z",
   "kind": "signal",
   "payload": {
    "signal": "three_up_hours",
    "transition": "enter",
    "price": 10.26,
    "definition_version": 6
   }
  },
  {
   "ticker": "PNBK",
   "ts": "2026-09-17T21:10:52.603Z",
   "kind": "signal",
   "payload": {
    "signal": "three_up_hours",
    "transition": "enter",
    "price": 0.975,
    "definition_version": 6
   }
  }
 ]
}

Same grammar on scan and webhooks. This signal is live-tense only — it isn't historized, so ?asof= reads and series pulls don't carry it.

Related signals — Intraday momentum