<?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 - Forums</title>
		<link>https://forum.developer.betfair.com/</link>
		<description>vBulletin Forums</description>
		<language>en</language>
		<lastBuildDate>Tue, 08 Sep 2026 04:01:47 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>https://forum.developer.betfair.com/images/misc/rss.png</url>
			<title>Developer Program Forum - Forums</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>
		<item>
			<title>Posting real bets with delayed app key</title>
			<link>https://forum.developer.betfair.com/forum/developer-program/general-betting/42982-posting-real-bets-with-delayed-app-key</link>
			<pubDate>Fri, 28 Aug 2026 20:45:40 GMT</pubDate>
			<description>Fejl24 blah blah blah</description>
			<content:encoded>Fejl24 blah blah blah</content:encoded>
			<category domain="https://forum.developer.betfair.com/forum/developer-program/general-betting">General Betting</category>
			<dc:creator>AndersSkovsborg</dc:creator>
			<guid isPermaLink="true">https://forum.developer.betfair.com/forum/developer-program/general-betting/42982-posting-real-bets-with-delayed-app-key</guid>
		</item>
		<item>
			<title>best_avail_back_sched_off - best_avail_lay_sched_off Diescrepency</title>
			<link>https://forum.developer.betfair.com/forum/developer-program/historical-data/42979-best_avail_back_sched_off-best_avail_lay_sched_off-diescrepency</link>
			<pubDate>Fri, 28 Aug 2026 04:21:30 GMT</pubDate>
			<description>I have downloaded the AU+NZ historical files and find there are over 800 records with the lay price less than the back price.  Has anyone else come...</description>
			<content:encoded><![CDATA[I have downloaded the AU+NZ historical files and find there are over 800 records with the lay price less than the back price.  Has anyone else come across this or know how to deal with it.<br />
<br />
Thank you]]></content:encoded>
			<category domain="https://forum.developer.betfair.com/forum/developer-program/historical-data">Historical Data</category>
			<dc:creator>billborric</dc:creator>
			<guid isPermaLink="true">https://forum.developer.betfair.com/forum/developer-program/historical-data/42979-best_avail_back_sched_off-best_avail_lay_sched_off-diescrepency</guid>
		</item>
		<item>
			<title>Does the delayed key preserve timeframe?</title>
			<link>https://forum.developer.betfair.com/forum/sports-exchange-api/exchange-api/42967-does-the-delayed-key-preserve-timeframe</link>
			<pubDate>Tue, 25 Aug 2026 09:29:48 GMT</pubDate>
			<description>Hello, I have two questions. 
 
- Does the DELAYED API key preserve the timeframe of events, i.e. are they sent to the stream in chronological order?...</description>
			<content:encoded><![CDATA[Hello, I have two questions.<br />
<br />
- Does the DELAYED API key preserve the timeframe of events, i.e. are they sent to the stream in chronological order?<br />
<br />
- Does the '.publish_time' return the time that the delayed key sent the data, or does it return the actual live time that the delayed key received the data (to later store for a few minutes before sending over).<br />
<br />
Thank you!<br />
<br />
EDIT: Another question, assuming it is in order, are there any updates missed in the time it takes to send? For example, live data of A -&gt; B -&gt; C, the delayed key won't send me A -&gt; C right? What if A - &gt; B occurs in the first 'batch', will there then be B -&gt; C in the later batch (a few minutes later), or will it skip to say G -&gt; H?]]></content:encoded>
			<category domain="https://forum.developer.betfair.com/forum/sports-exchange-api/exchange-api">Exchange API</category>
			<dc:creator>forestBETTING</dc:creator>
			<guid isPermaLink="true">https://forum.developer.betfair.com/forum/sports-exchange-api/exchange-api/42967-does-the-delayed-key-preserve-timeframe</guid>
		</item>
		<item>
			<title>New Field betDelayModels Added to Historical Data Files from 17th August 2026</title>
			<link>https://forum.developer.betfair.com/forum/developer-program/historical-data/42949-new-field-betdelaymodels-added-to-historical-data-files-from-17th-august-2026</link>
			<pubDate>Thu, 20 Aug 2026 09:29:12 GMT</pubDate>
			<description>The new field betDelayModels will be available in the Betfair Historical Data service market files after the date 17/08/26 
 
Please note that...</description>
			<content:encoded><![CDATA[<span style="font-family:Arial">The new field betDelayModels will be available in the Betfair Historical Data service market files after the date 17/08/26<br />
<br />
Please note that following field will be available on all messages where publish time is greater than or equal to 17/08/26 10:00 BST<br />
<br />
Also note that files for markets that span across the point 17/08/26, 10:00 BST will contain market definition messages without this new field up until 17th of August 2026 10:00 BST and with the new field after17th of August 2026 10:00 BST</span><ul><li><span style="font-family:Arial">&quot;betDelayModels&quot;: [] or absence of this field, indicates - Only traditional model of bet delay enabled</span></li>
<li><span style="font-family:Arial">&quot;betDelayModels&quot;: [PASSIVE] - Passive Delay enabled for the market</span></li>
<li><span style="font-family:Arial">&quot;betDelayModels&quot;: [DYNAMIC] - Dynamic Delay enabled for the market</span></li>
<li><span style="font-family:Arial">&quot;betDelayModels&quot;: [PASSIVE,DYNAMIC] - Both Passive and Dynamic delays enabled for the market</span></li>
</ul><span style="font-family:Arial">Please see the latest Betfair Historical Data feed specification document attached.</span><br />
<br />
<span style="font-family:Arial"><span style="color:#1e1e1e">Kind Regards</span><br />
<br />
<b><span style="color:#1e1e1e">Betfair Developer Program</span></b></span>]]></content:encoded>
			<category domain="https://forum.developer.betfair.com/forum/developer-program/historical-data">Historical Data</category>
			<dc:creator>Betfair Developer Program</dc:creator>
			<guid isPermaLink="true">https://forum.developer.betfair.com/forum/developer-program/historical-data/42949-new-field-betdelaymodels-added-to-historical-data-files-from-17th-august-2026</guid>
		</item>
	</channel>
</rss>
