<?xml version="1.0" encoding="windows-1252"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Developer Program Forum - Software Vendor Program</title>
		<link>https://forum.developer.betfair.com/</link>
		<description>Do you have a question for members of the Software Vendor community? Do you have a feature request or unique development needs? Please post questions here.</description>
		<language>en</language>
		<lastBuildDate>Fri, 04 Sep 2026 04:43:18 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>https://forum.developer.betfair.com/images/misc/rss.png</url>
			<title>Developer Program Forum - Software Vendor Program</title>
			<link>https://forum.developer.betfair.com/</link>
		</image>
		<item>
			<title>Live Pricing (ESA):</title>
			<link>https://forum.developer.betfair.com/forum/developer-program/software-vendor-program/42985-live-pricing-esa</link>
			<pubDate>Thu, 03 Sep 2026 19:23:33 GMT</pubDate>
			<description>I am currently developing a multi-tenant commercial web application for Betfair customers. 
Our backend architecture is designed to minimise server...</description>
			<content:encoded><![CDATA[<br />
I am currently developing a multi-tenant commercial web application for Betfair customers.<br />
Our backend architecture is designed to minimise server infrastructure overhead and betfair server usage. I am configuring our systems to use my <b>Delayed App Key</b> for development and connection testing, with the architecture built to swap to our <b>Live Vendor Key</b> once certified.<br />
Before i finalise our live data layer, i want to ensure our data distribution model is fully compliant with the Betfair Vendor Program guidelines.<br />
my Proposed Architecture (mental model):<ol class="decimal"><li><b>Market Metadata:</b> my backend uses our Vendor credentials to pull listMarketCatalogue and cache event frameworks in MongoDB/Redis.</li>
<li><b>Live Pricing (ESA):</b> 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.</li>
<li><b>Data Flow:</b> 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.</li>
</ol>my Questions:<ol class="decimal"><li>Does Betfair permit this &quot;Token-Pinned Master Stream&quot; model where a shared backend stream is authenticated via an active user's ssoid to populate a localized cache for active users?</li>
<li>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?</li>
<li>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?</li>
</ol>i want to ensure my platform is completely aligned with your commercial requirements from day one. Thank you for your time and guidance.]]></content:encoded>
			<category domain="https://forum.developer.betfair.com/forum/developer-program/software-vendor-program">Software Vendor Program</category>
			<dc:creator>kimpolley</dc:creator>
			<guid isPermaLink="true">https://forum.developer.betfair.com/forum/developer-program/software-vendor-program/42985-live-pricing-esa</guid>
		</item>
	</channel>
</rss>
