Skip to main content

Bifrost Integration Chat — 2026-03-18 (Wednesday)

Channel: #forsyt-bm-integration (Suntech Innovation Slack)

Michael Cheremuhin — 2:53 PM

hi @Bhargav. something from conformance team:

Open issues that we think are important to fix: • When a member clicks a line or price, this appears in the betslip (correct behaviour) ◦ If we change prices, this is not reflected in betslip (correct behaviour) ◦ When customer sends bet, the bet is accepted at the price and line that Artemis is at the time even if it is worse than what was requested in betslip (it should be rejected at Artemis if worse and Artemis will give better odds if better for customer) ◦ It feels like you are sending the request price and line as blank perhaps and we just accept the bet at the line and price we are at? - please check this, as it might be kinda cheating customers as we can accept on worse prices ◦ The line is not shown to the customer in open bets so customer may get a surprise in settlement (they should show the line in their betlist). This was handled correct on the site last week. • Post settlement voiding ◦ This works around 50% of the time ◦ When it doesn’t work, it is double counting the change instead of reverting back to the pre-bet balance ◦ E.g. $20k balance, bet $1k@100, settle as winner, balance 21k. Void bet, balance goes to 19k sometimes instead of 20k

Thread (2 replies):

Bhargav — 6:57 PM Working on these

Bhargav — 4:09 PM @Michael Cheremuhin Can you let me know if all these issues are addressed?

Bhargav — 6:59 PM

@Michael Cheremuhin Do we have any bifrost Markets on production right now? We are not seeing any markets. https://forsyt.io/fixture/35385015?sportId=27

forsyt.io | Private Sports Trading Platform Private sports exchange built for speed and designed for trust. Trade your edge with the sharpest odds, credit-based settlements, and AI-powered insights.

Michael Cheremuhin — 7:05 PM

@Bhargav i can see match odds market closed. you don't see any markets from us or you don't see any open markets from us?

Thread (13 replies):

Bhargav — 7:08 PM We see market data flowing on your preprod feed (5,600+ OPEN updates in 5 min on our dev env), but your production feed (mq.bifrost.bet:5577) has gone quiet — in the last 10 minutes we received only ~11 book updates, all with status=CLOSED and eventId=NONE. Zero OPEN markets for any event.

Bhargav — 7:09 PM The last OPEN market book we received on prod was at ~13:21 UTC (event 22.150246, KNI vs Lions). After that, everything went CLOSED.

Bhargav — 7:09 PM Yesterday everything was coming well when I tested but today I think it has gone silent

Michael Cheremuhin — 7:10 PM let me check

Michael Cheremuhin — 7:12 PM i can see Pakistan National T20 Cup Karachi Region Whites v Abbottabad Region should be open now

Michael Cheremuhin — 7:12 PM 35385552

Michael Cheremuhin — 7:13 PM mapping id 22.154535

Michael Cheremuhin — 7:13 PM do you have that event from us?

Michael Cheremuhin — 7:15 PM can you please run recovery flow to see if events and markets are resent to you

Bhargav — 7:34 PM @Michael Cheremuhin We found the issue on our side. Quick question on how your event IDs work:

For the Karachi Region Whites v Abbottabad Region match, we received two different events from the event queue, both with the same Betfair externalId 35385552:

  1. eventId: 9.40432 — arrived at 21:30 UTC
  2. eventId: 22.154535 — arrived at 21:38 UTC

All market catalogues and books reference 22.154535 as their eventId. Nothing references 9.40432.

Our code locked the Betfair mapping to the first event (9.40432) and refused to update it when 22.154535 arrived — so when we look up markets for this fixture, we find nothing because 9.40432 has zero markets.

We see this same pattern on every match (e.g. 9.40431 vs 22.150246 for KNI vs Lions).

Questions:

  1. What is the difference between the 9.x and 22.x event IDs? Is 9.x a series/competition-level thing and 22.x the actual match?
  2. Should we always prefer the latest event that shares the same externalId? Or is there a better way to know which event will have the markets?
  3. Your docs say the externalIds mapping is "not static nor unique" — does that mean we should always update to the latest mapping?

Michael Cheremuhin — 7:35 PM hm that's strange. 9. is internal mapping, 22. is external mapping

Michael Cheremuhin — 7:36 PM overall please use 22. but let me check why 9. are sending out

Michael Cheremuhin — 3:12 AM @Bhargav we've checked the issue and found the cases when internal id was sent before mapping id. overall yes, please use the latest event message. if that suites your system - merge mapping ids on your side, that might be useful for the next integrations from us. nevertheless, that issue hot fix was delivered to production. please let us know if it's faced