View as markdown
Concepts › Signals › Price › Support & resistance

at_support

Price is testing a detected support level.

Watch this signal live on real tickers: Open in Explore →

At a glance

Definition
Price within 1.5 × ATR(20) of an active detected support level — a cluster of two or more historical swing lows within an ATR-scaled band, still unbroken.
Typestate (boolean)
GroupPrice
CategorySupport & resistance
Update cadence1 min · mkt hrs
Intervals1m/1h/1d
Universeall tickers
Historynone
Firingcontinuous
Typical rolecompound filter · chart annotation · entry-timing 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 →

Live — every ticker where it fires now
curl "https://api.tickerbot.io/v2/signals/at_support" \
  -H "Authorization: Bearer YOUR_KEY"
As-of — the same read at a past date
curl "https://api.tickerbot.io/v2/signals/at_support?asof=2026-05-22" \
  -H "Authorization: Bearer YOUR_KEY"
Subscribe — webhook when a ticker starts matching
curl -X POST "https://api.tickerbot.io/v2/signals/at_support/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 →

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": "at_support" }'
As-of — the same scan at a past date
curl -X POST "https://api.tickerbot.io/v2/scan" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_KEY" \
  -d '{ "q": "at_support", "asof": "2026-05-22" }'
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": "at_support", "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 →

History — the column on an aligned time grid
curl "https://api.tickerbot.io/v2/series?tickers=AAPL,MSFT&columns=close,at_support" \
  -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 →

Firings — every enter edge as a point event
curl -G "https://api.tickerbot.io/v2/events" \
  -d "kind=signal" -d "signal=at_support" -d "transition=enter" -d "from=2026-01-12" \
  -H "Authorization: Bearer YOUR_KEY"
Spans — when it was true for one ticker (AAPL)
curl "https://api.tickerbot.io/v2/signals/at_support/AAPL/events" \
  -H "Authorization: Bearer YOUR_KEY"

Same grammar on scan, series, and webhooks; state reads take ?asof= for point-in-time answers.

Related signals — Support & resistance