at_resistance
Price is testing a detected resistance level.
At a glance
Price within 1.5 × ATR(20) of an active detected resistance level — a cluster of two or more historical swing highs within an ATR-scaled band, still unbroken.| Type | state (boolean) |
| Group | Price |
| Category | Support & resistance |
| Update cadence | 1 min · mkt hrs |
| Intervals | 1m/1h/1d |
| Universe | all tickers |
| History | none |
| Firing | continuous |
| Typical role | compound filter · chart annotation · level-rejection setup ingredient |
Pivot-detected price levels a ticker has repeatedly touched, and whether price is at one now. Levels are found nightly across the equity universe; a ticker with too little history has none and its flags read NULL rather than false.
Query it
Every applicable form factor, grouped by endpoint family. Swap YOUR_KEY for the value from /dashboard/keys. Response payloads are real captures, sampled 2026-08-18 and trimmed — your run's values and dates will differ.
Use signals /v2/signals/{signal}
One signal across the market: who matches now, who matched then, and a push when someone starts. Docs →
curl "https://api.tickerbot.io/v2/signals/at_resistance" \
-H "Authorization: Bearer YOUR_KEY"curl "https://api.tickerbot.io/v2/signals/at_resistance?asof=2026-05-22" \
-H "Authorization: Bearer YOUR_KEY"curl -X POST "https://api.tickerbot.io/v2/signals/at_resistance/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.
Use scan /v2/scan
The whole market through a WHERE clause — this signal composed freely with any other column. Docs →
curl -X POST "https://api.tickerbot.io/v2/scan" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{ "q": "at_resistance" }'curl -X POST "https://api.tickerbot.io/v2/scan" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{ "q": "at_resistance", "asof": "2026-05-22" }'curl -X POST "https://api.tickerbot.io/v2/scan/subscribe" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{"q": "at_resistance", "target_url": "https://example.com/hooks/tickerbot"}'Returns 201 with the created webhook object; deliveries carry the tickers matching the condition at each evaluation.
Use series /v2/series
Its history over time, on one aligned grid. Docs →
curl "https://api.tickerbot.io/v2/series?tickers=AAPL,MSFT&columns=close,at_resistance" \
-H "Authorization: Bearer YOUR_KEY"Use events /v2/events
The flag as a timeline: each edge as a point event, and the spans it stayed true. Docs →
curl -G "https://api.tickerbot.io/v2/events" \
-d "kind=signal" -d "signal=at_resistance" -d "transition=enter" -d "from=2026-01-12" \
-H "Authorization: Bearer YOUR_KEY"curl "https://api.tickerbot.io/v2/signals/at_resistance/AAPL/events" \
-H "Authorization: Bearer YOUR_KEY"Same grammar on scan, series, and webhooks; state reads take ?asof= for point-in-time answers.