View as markdown
Concepts › SignalsEvents Splits & share changes

dilution_30d

Shares outstanding rose more than 3% over the last 30 days.

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

At a glance

Definition
shares_outstanding > 30d-ago × 1.03
Typestate (boolean)
GroupEvents
CategorySplits & share changes
Update cadencepost-close daily
Universeall tickers
Historynone — live row only, not historized (no as-of reads)
Firingcontinuous

Events that alter share count or float: splits, buybacks, dilution.

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/dilution_30d" \
  -H "Authorization: Bearer YOUR_KEY"
Response (sampled 2026-08-18, trimmed)
{
 "as_of": "2026-08-18T00:23:26.686Z",
 "signal": "dilution_30d",
 "condition": null,
 "universe": null,
 "count": 0,
 "results": []
}
Subscribe — webhook when a ticker starts matching
curl -X POST "https://api.tickerbot.io/v2/signals/dilution_30d/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 -G "https://api.tickerbot.io/v2/scan" \
  --data-urlencode "q=dilution_30d" \
  -H "Authorization: Bearer YOUR_KEY"
Response (sampled 2026-08-18, trimmed)
{
 "as_of": "2026-08-18T00:23:27.125Z",
 "query": {
  "q": "dilution_30d",
  "limit": 2,
  "order": "day_change_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": "dilution_30d", "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 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=dilution_30d" -d "transition=enter" -d "since=2026-01-10" \
  -H "Authorization: Bearer YOUR_KEY"
Response (sampled 2026-08-18, trimmed)
{
 "as_of": "2026-08-18T00:23:27.308Z",
 "query": {
  "kind": "signal",
  "tickers": null,
  "universe": null,
  "since": "2026-01-10T00:00:00.000Z",
  "until": null,
  "limit": 2,
  "signal": "dilution_30d",
  "transition": "enter"
 },
 "count": 0,
 "results": []
}
Spans — when it was true for one ticker (AAPL)
curl "https://api.tickerbot.io/v2/signals/dilution_30d/AAPL/events" \
  -H "Authorization: Bearer YOUR_KEY"
Response (sampled 2026-08-18, trimmed)
{
 "as_of": "2026-08-18T00:23:27.474Z",
 "ticker": "AAPL",
 "signal": "dilution_30d",
 "count": 0,
 "events": []
}

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

Related signals — Splits & share changes