Growing Discord community — direct access to the developer, live coverage & picks. Join the Discord Join now →

Roadmap & Feedback

Vote on what we build next — Founder votes count 3× · report a bug / ask something →
🥵 Aura leaderboard
1 Giove 444
2 FreeApi 🎖️ 413
3 LDA-SCOUTING 185
4 polse 🎖️ 160
5 martinmgs 🎖️ 132
6 srfcboy 🎖️ 124
7 g@@ 116
8 muzaffer72 115
9 Asakara 🎖️ 98
10 [email protected] 🎖️ 95

Feature requests

20 open
Clarify API data usage, retention and derived-work rights
We would like Bzzoiro to publish a clear “API Data Usage / License” section in its Terms or API documentation. For professional R&D users, it would be very helpful to explicitly clarify whether data lawfully obtained through the Bzzoiro API or WebSocket may be: • stored and retained for internal use; • archived as historical snapshots to study data updates and revisions over time; • used for internal R&D, statistical analysis, backtesting, model development and model evaluation; • processed as input/context for AI and machine-learning systems; • used to create derived outputs such as analytics, scores, indicators, probabilities, forecasts and models; • retained after an API subscription or access period ends for research reproducibility, historical analysis and audit purposes. We do not need permission to resell, mirror or redistribute Bzzoiro’s raw API feed. Raw-data redistribution can remain prohibited. It would also be useful to clarify that third-party media assets such as logos, photographs or images may have separate rights and are not necessarily covered by the structured-data permissions. Ideally, the policy should have an effective date or version number so that users can document which terms applied when data was collected. This clarification would make it much easier for professional users to adopt Bzzoiro for legitimate R&D and AI/model-development use while respecting Bzzoiro’s data rights.
General / Account In Progress 🎖️ 3 Founder
Idea: an 'Odds Pro' add-on for modelling and CLV (history, closing line, sharp books, bulk)
Your free odds are already great for display. For people who model and track results (closing line value, calibration against the market) the gap is depth, history and guarantees, which is what dedicated odds APIs (The Odds API, OddsPapi, OddsJam-style feeds) sell. An optional paid 'Odds Pro' add-on, separate from the free tier, could cover it: 1. Odds history per bookmaker: GET /odds/history/?event_id=&market=&bookmaker= returning every price change as a time series (price, observed_at, is_live), kept after the match ends. Today a finished match only shows its last (in-play) quote. 2. Closing line: closing_decimal_odds + closing_at per bookmaker/market/outcome, = last pre-match quote (ties in with ticket #402). 3. Sharp references: Pinnacle and an exchange price (you already capture exchange data for Weight of Money) flagged as `sharp: true`, plus a de-vigged `fair_odds` / `fair_probability` per outcome computed from them. That is the reference everyone rebuilds by hand. 4. Depth and freshness: n_books per market, per-quote updated_at, filters min_books / max_age (see my ticket on consensus depth). 5. Bulk snapshot: GET /odds/snapshot/?date=YYYY-MM-DD&markets=1X2,OU,BTTS returning every event of the day in one paginated call, instead of one call per event. 6. Refresh guarantee near kickoff: e.g. every 1-2 min in the last 2 hours pre-match, documented per league, and a coverage endpoint /odds/coverage/?league= with the median number of books per market, so users know which leagues are deep enough before building on them. 7. Push on line moves (optional): webhook or WebSocket frame when a consensus price moves more than X% or a market opens/suspends. 8. Basketball with the same model (moneyline, totals, spread), see my basketball odds ticket. Why: with 1-3 and 5 alone, a user can measure CLV and back-test against the market entirely on BSD, with your event ids and no matching. Those are the features people pay odds APIs for today, and you already hold most of the raw data. Thanks!
Football In Progress
New odds markets: team goals over/under (home/away totals), correct score, O/U 4.5-5.5
Follow-up to #420 (multigol, not carried by your source, understood). Three goal markets that are widely quoted, and that would cover most of the same use cases: 1. Team goals over/under (a.k.a. team totals): goals scored by ONE team, home or away. Suggested codes following yours: `over_under_home_05/15/25/35`, `over_under_away_05/15/25/35` (or `team_total` with team=HOME/AWAY and the line in `line`, like total_corners). Outcomes over/under. First half as a bonus. 2. Correct score full time (0-0, 1-0 ... 4-4, 'other'), outcomes as score strings, per bookmaker like the other markets. 3. Higher match totals: over_under_45 and over_under_55 next to the existing 05-35. Where it already exists: another odds API I use carries these from 100+ bookmakers on ordinary fixtures (team O/U 1.5 alone around 100 books, team O/U 0.5/2.5/3.5 and correct score at 20-60), and the big Italian/European books (bet365, Sisal, Snai...) all quote them pre-match. So the source side should not be the blocker this time; if your feed carries them under another name, mapping them would be enough. Why it matters: - Team totals are the cleanest goal market when one side is much stronger ('Home over 1.5', 'Away under 0.5') and avoid the noise of the opponent scoring. - Correct score is the full joint distribution of the result: summing its de-vigged probabilities gives a fair price for ANY goal range (multigol 2-4 = sum of all scores with 2-4 goals), team totals, win-to-nil, etc. That answers the multigol use case without needing a multigol feed. - O/U 4.5/5.5 completes the total-goals ladder (today it stops at 3.5). Same fields as the other markets please (decimal_odds, opening price, updated_at, is_live). Thanks!
Football In Progress
API questions
Hello Support Team, We are integrating your sports data and odds services into our sportsbook platform, 888juventus.club, and would appreciate detailed technical guidance on three areas: extended betting markets, live match tracking, and real-time odds and settlement safety. 1. Extended Pre-Match and Live Odds Markets Currently, we receive only basic markets such as 1X2, Double Chance, BTTS, and standard Over/Under goals. We want access to all additional available markets, including: * Asian Handicap and Asian Total Goals * Extended Over/Under lines (0.5–8.5+) * First-Half and Second-Half markets * Half-Time/Full-Time results * Correct Score and Team Total Goals * Corners and Cards * First/Last/Anytime Goalscorer * First Team to Score and Odd/Even Goals * Combination markets (BTTS + Over/Under, Result + Goals) * All other available special markets Questions: 1. Which endpoints retrieve the complete pre-match and live odds markets for an event? 2. Are extended markets included in our subscription, or do we need additional access? 3. Which parameters, market IDs, bookmaker IDs, or filters are required? 4. Is there an endpoint listing all available market types and identifiers? 5. How can we retrieve every outcome and handicap/total line without missing selections? 6. Are odds separated by bookmaker? How should we maintain a consistent bookmaker source? 7. Are there pagination limits, response-size limits, or market restrictions? 8. Do pre-match and live markets use different endpoints or data structures? 9. Can you provide working API requests and complete JSON examples? 2. Live Match Tracker and Albanian Language We want a real-time match tracker displaying: * Match clock, period, and current/half-time scores * Goals, goalscorers, cards, substitutions, penalties, and VAR * Corners, possession, shots, attacks, and dangerous attacks * Match timeline and significant events * Match status: scheduled, live, half-time, suspended, postponed, finished The interface should support Albanian (sq / sq-AL). Questions: 1. Do you provide an embeddable live match tracker widget, or must we build our own using your API? 2. Does the widget support Albanian? 3. If not, can we translate all labels and event descriptions ourselves? 4. Are standardized event codes available for custom translations? 5. Can we receive real-time match events and statistics via WebSocket or push updates? 6. How are canceled goals, VAR reversals, and corrected scores communicated? 7. Are tracker events and betting odds linked by the same event IDs? 8. Can you provide documentation and an example implementation? 3. Real-Time Odds Updates, Results and Betting Safety Our highest priority is ensuring that bets use current, valid odds and that suspended markets cannot accept wagers. We aim for approximately 100 ms update latency, where technically supported, and understand that actual latency depends on your infrastructure. A. Update frequency and latency 1. What are the actual update frequencies for pre-match and live odds? 2. What are the typical and maximum delays between a source odds change and API delivery? 3. Is 100 ms supported? What interval do you recommend? 4. Do you offer WebSocket, streaming, webhook, or other push-based updates? 5. If polling is required, what is the minimum permitted interval and API rate limit? 6. Are updates incremental, or must we fetch complete event snapshots? 7. Do you provide sequence numbers, timestamps, or version IDs to detect missing or out-of-order updates? 8. How should we recover missed updates after a connection interruption? B. Market suspension and closure 1. Which exact fields and values indicate an event, market, or selection is active, suspended, closed, removed, settled, or voided? 2. How quickly are odds suspended after a goal, penalty, red card, VAR review, or match interruption? 3. Are markets automatically suspended during critical match events? 4. How do we detect when a suspended market reopens? 5. How should we transition from pre-match to live odds at kickoff? 6. Are pre-match markets automatically closed when a match starts? 7. If a market disappears from an API response, does this mean suspended, removed, or unchanged? C. Bet validation and stale-odds protection 1. Do you offer an official odds validation/revalidation endpoint before accepting a bet? 2. How can we verify the latest odds at the exact moment of submission? 3. Should we validate using odds ID, market ID, selection ID, timestamp, or odds version? 4. What should happen if odds change between selection and submission? 5. How should we handle a market suspended during bet submission? 6. Is there a recommended live betting delay? 7. Is there an authoritative server-side snapshot or status to verify before accepting a wager? 8. What safeguards prevent bets being accepted after goals, suspensions, or event closure? D. Results and settlement 1. Which endpoints provide official and final match results? 2. How frequently are scores and results updated? 3. How are score corrections, VAR reversals, abandoned matches, and postponements communicated? 4. Do you provide official settlement results for each market and selection? 5. How do we identify winning, losing, voided, and pending selections? 6. Is there a settlement feed supporting corrections or revisions? 7. Which source should be considered authoritative for final settlement? 8. Are event IDs consistent across pre-match, live odds, tracker data, and results? 4. Documentation and Recommended Architecture Please provide: * Complete documentation for extended pre-match and live markets * Market status, suspension, and closure specifications * WebSocket/streaming documentation, if available * Live match tracker and event data documentation * Results and settlement API documentation * Rate limits and recommended update intervals * Example JSON for odds changes, suspensions, and event updates * Recommended production architecture for low-latency updates and safe bet validation We would appreciate specific endpoint URLs, request parameters, response fields, and working examples rather than general explanations. Our goal is to support the widest available range of betting markets while ensuring accurate odds, reliable live match data, and secure bet acceptance. Thank you for your assistance. Best regards, Technical Team 888juventus.club
Football In Progress
Shipped & closed (87)

📦 Shipped

Got something to say?

Sign in to post
The board above is open to everyone. Ideas, bugs and votes need an account so we can reply to you and so votes count once each.
Sign in Create a free account