Skip to main content
A dropping odd is an outcome whose decimal price drops (shortens) meaningfully over time — e.g. a home win going from 2.50 to 2.10. A shorter price means a rising implied probability: money is coming in on that side. Since Pinnacle is the sharpest book, these moves often signal market information (injury, lineup, a steam move).

Why it’s a signal

  • Informed money: at Pinnacle a sharp drop reflects large/informed stakes, not noise.
  • Positive CLV: betting before the price shortens further beats the close (see true odds).
  • Live timing: in‑play, dropping odds react to match events within seconds.

Detecting them with apinn

Every /api/odds?full_history=1 call returns all snapshots of an event (each timestamped), with raw odds1/odds0/odds2 and devig todds1/0/2. Compare the opening (first snapshot) to the current value:
1

List live matches

2

Fetch the odds history

3

Compute the drop per outcome

drop% = (open − current) / open × 100 — keep drops ≥ your threshold.
Python
Prefer the todds fields (margin removed) for a cleaner signal: the drop then reflects the move in fair probability, not the vig.

Best practices

  • Bound the odds (e.g. 1.30–6.00): ignore noisy extremes.
  • Window: since the open (underlying move) or over the last N minutes (live reaction).
  • Real-time: for sub‑second, listen to the SSE stream instead of polling.
  • Inverse: rising odds (prices drifting out) signal money leaving a side.

Build it in one prompt

Don’t want to code? Paste our ready‑made prompt into Claude and it builds the dropping-odds monitor for you — see Build with Claude.