Live Pricing (ESA):

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kimpolley
    Junior Member
    • Sep 2026
    • 1

    #1

    Live Pricing (ESA):


    I am currently developing a multi-tenant commercial web application for Betfair customers.
    Our backend architecture is designed to minimise server infrastructure overhead and betfair server usage. I am configuring our systems to use my Delayed App Key for development and connection testing, with the architecture built to swap to our Live Vendor Key once certified.
    Before i finalise our live data layer, i want to ensure our data distribution model is fully compliant with the Betfair Vendor Program guidelines.
    my Proposed Architecture (mental model):
    1. Market Metadata: my backend uses our Vendor credentials to pull listMarketCatalogue and cache event frameworks in MongoDB/Redis.
    2. Live Pricing (ESA): To avoid opening hundreds of separate TCP/WebSocket connections for every individual web customer (which would exhaust server resources and flood Betfair with redundant connection requests), we intend to use a centralized caching model.
    3. Data Flow: Our backend will open a minimal pool of Master Stream connections to the Betfair Exchange Stream API (ESA), authenticate the subscription via an active, logged-in customer's session token (ssoid), and stream the price deltas into a central Redis cache. Our web app will then broadcast those updates to our active users internally via lightweight WebSockets.
    my Questions:
    1. Does Betfair permit this "Token-Pinned Master Stream" model where a shared backend stream is authenticated via an active user's ssoid to populate a localized cache for active users?
    2. If this is acceptable, does your team have a preferred best practice for seamlessly handling authentication handovers on an active stream when a user session expires?
    3. If this model violates data redistribution clauses, what is Betfair's recommended architectural pattern for scalable, multi-tenant web applications to consume the Stream API without triggering connection limits?
    i want to ensure my platform is completely aligned with your commercial requirements from day one. Thank you for your time and guidance.
  • Betfair Developer Program
    Forum Administrator
    • Sep 2008
    • 35

    #2
    Hi kimpolley

    If you are developing a "multi-tenant commercial web application for Betfair customers" please contact us directly regarding licensing via the following process - https://support.developer.betfair.co...oftware-Vendor

    All relevant Vendor Web API documentation, including a flow diagram can be found via https://betfair-developer-docs.atlas...I#vendorwebapi

    When configured, when operating under the Vendor Web API architecture, each user has a specific number of connections (i.e. market subscriptions) assigned.

    Please see below the relevant product and sot ware vendor licensing requirements that address the specific points you've made
    • All requests including real-time market, volume and price data requests must be made by the end-user account.
    2.3 It is a condition of this Agreement that the User shall not do any of the following:............................
    • (o) provide products which aggregate or hide individual Betfair customer activity normally available to Betfair through individual use of the Betfair API or website without prior written consent from Betfair and without ensuring that they keep a record of that activity. An example would be where a User reads Betfair prices and pushes them out to its customers in such a way that Betfair can no longer see the individual price reading of customers via the Betfair API market refresh services;
    Kind Regards

    Neil


    Comment

    Working...
    X