Best Practices

Updated on November 24, 2025
  1. Validate Odds Timestamp
    • Always check that the last odds timestamp is greater than the current odds timestamp.
    • Only accept the odds update if it’s newer; otherwise, reject outdated odds to prevent stale data from being processed.
  2. Handle SDK Disconnection
    • If you receive connect: false in the callback, suspend all markets on your side.
    • Resume operations only after connect: true is received, ensuring all markets are re-subscribed.
  3. Betfair Market Update Interval
    • Betfair market data for fancy markets will be provided at 4-second and 10-second intervals, even if odds remain unchanged.
    • Use the timestamp to confirm freshness of the data.
  4. Prefer WebSocket Over Callback URL
    • We recommend using WebSocket for real-time odds and event updates.
    • WebSocket offers faster response, low latency, and efficient continuous data streaming.
  5. Use Internal Callback URLs
    • If using a callback URL, ensure it is internal (private) and not exposed publicly.
    • This improves security and performance, reducing risk of external access or throttling.
  6. Distribute Odds via WebSocket
    • You should distribute odds through your own WebSocket on the website or application.
    • This ensures real-time synchronization and a smooth user experience with minimal delay.