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

API questions

Feature Request Football In Progress Nov 17, 2026 · 888juventus · 🥵 5 aura
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

Comments

1
Nora · BSD Support (AI) · Admin · AI Nov 17, 2026 19:11
Hi, thanks for the detailed list. I'll be straight with you first, because your priority is bet safety: BSD is a sports data API, not a betting-grade odds feed, and several things you ask for do not exist here. I checked each point against our docs and the live API. Not available today, so please do not build bet acceptance on us: - Odds are re-read on a schedule of tens of minutes near kickoff and hours earlier on, then cached for about 3 minutes on the REST odds endpoints. The WebSocket odds frame checks about every 30 seconds, but it only changes when our underlying read changes. 100 ms odds latency is not supported. - There are no suspended/closed/settled/void flags on markets or selections, no sequence numbers or odds versions, no revalidation endpoint, no settlement feed and no per-market settlement results. A market missing from a response does not mean suspended. - Our license says the data is provided as-is and is not warranted for wagering decisions, and you are responsible for the gambling rules that apply to you. There is no separate licence or SLA for sportsbooks. For live betting you would need a provider built for that, with suspension and settlement guarantees. What we do have (football): - Odds: GET /api/v2/odds/ (filters: event_id, league_id, market, outcome, bookmaker_slug, updated_after) and GET /api/v2/events/{id}/odds/ for one match. Markets quoted: 1X2, total goals 0.5 to 4.5, BTTS (each for full time, 1st half, 2nd half), double chance, draw no bet, Asian handicap (-3.5 to +3.5 in quarters, with a push field), total corners 7.5 to 11.5, clean sheet and win to nil. Not available: correct score, half-time/full-time, goalscorers, odd/even, combo markets, team totals, and cards (not priced). Over/under above 4.5 is not quoted either. - Per-bookmaker prices and the comparison grid need Football Unlimited; your account does not have it right now, so you only get the consensus price. 21 bookmakers are priced, listed at /api/v2/bookmakers/. Odds are separated by bookmaker with that plan; use one bookmaker_slug consistently. Pagination is limit/offset. - Pre-match and live use the same odds rows, marked by is_live. The free daily quota is 7,500 requests per account, plus a burst limit of 25 requests per second per IP on cached endpoints. Poll live lists no faster than every 10 s. - Live tracking: GET /api/v2/events/live/ and the incidents, commentary and stats endpoints of each event. Statuses are upcoming, live, finished, cancelled, postponed, unresolved. Event ids are the same across odds, live and results. - Push: the WebSocket add-on at wss://sports.bzzoiro.com/live/football/ (score, clock, stats, odds, and per-action frames on matches flagged websocket_plus). Add-on pricing is at /addons/. If you reconnect, the subscribe reply carries a snapshot and recent history, so you can recover state. Corrections arrive as new frames (deleted_event for disallowed goals, rescinded_card), and every action frame carries the score as of that action. - Final results: home_score, away_score and status on GET /api/v2/events/{id}/. Scores can be corrected upstream, so re-read after full time. Tracker and Albanian: we have no embeddable tracker widget (only the Arena 3D viewer with the WebSocket add-on, which is not a labels-based tracker). You build the interface from the API, and event types are fixed English codes you can map to your own Albanian labels. Commentary text is in English only. Complete docs, with JSON examples, are at https://sports.bzzoiro.com/docs/ (football/odds-predictions, football/events, websocket/football, conventions). If football data for display (fixtures, scores, stats) is what you need, we can help with that. If you tell me which of these you need, I can go deeper on it. Nora · BSD Support (AI)
Log in to comment.