Bifrost Integration Chat — 2026-02-16 (Monday)

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

Oleksandr Alieksieiev joined the channel — 12:50 AM

Bhargav — 1:00 PM

@Michael Cheremuhin Good Morning. We have started the BiFrost integration. Please help answer the above questions. Can you share the API key and whitelist our IPs to start testing and integration?

Michael Cheremuhin — 1:13 PM

@Bhargav hi! glad to see you in our integration channels. will get back on your questions a bit later today after launching the week. meanwhile, please share your IP addresses for whitelisting so we can prepare your accesss. and yes, we can also provide within the same API exchange markets for cricket, soccer and tennis, more sports coming soon.

Bhargav — 2:22 PM

108.61.221.157 45.76.139.124

Michael Cheremuhin — 4:11 PM

so, while the access is being minted by devops team, let me get back to current questions

Michael Cheremuhin — 4:18 PM

> 1. Does Bifrost RabbitMQ queue messages arrive as JSON also or Protocol Buffers only? we are using protobuf format due to it's small fingerprint and less CPU consumption during processing. especially if you are going to take exchange markets from us, it brings a lot of advantages. I think every single language has a ready to use library to convert protos into classes, let me know if you need any help with your particular language.

> 2. The PlaceBetRequest has a required providerId field. What value should forsyt send? Is this identifying which upstream exchange Bifrost routes to internally, or is it our client identifier? no, there is no providerId. the sample requests are correct, seems like it slipped in into the fields reference table, let me remove it.

> 3. The ipAddress field is required on PlaceBetRequest. Should we pass the actual end-user's IP address (from HTTP headers), or a static server/platform IP? we'd prefer end-user's IP addresses for fraud control considerations

> 4. Does Bifrost have a cancel bet REST endpoint? The docs show CANCEL_PENDING and CANCELLED statuses on BetSnapshot, but only documents the placement endpoint. Without this, we can't support bet cancellation with Bifrost. bets cancelation is possible only for exchange markets as for sportsbook it's all or nothing

> 5. Do you support the exchange markets as well along with bookmaker markets? If yes, what all exchange markets are you supporting and do we have access to them? let me send you the full integration guide covering exchange content as well

Michael Cheremuhin — 4:21 PM

please find the full docs. providerId is also removed. that was a temporary field due to our internal migrations between trading tools which is now completed

📎 BFST-Bifrost API Public Documentation-160226-104956.pdf (pdf, 3051KB)

Michael Cheremuhin — 4:30 PM

please find the connection details:

Bifrost Preprod RabbitMQ ssl: false
Bifrost Preprod RabbitMQ virtual host: /customers
Bifrost Preprod RabbitMQ username: forsyt_preprod
Bifrost Preprod RabbitMQ password: N49wBBb7GLfyPYKj
Customer topics prefix: forsyt

Bifrost Preprod Placebet API access token: forsyt_preprod

whitelisted IPs:
 - 108.61.221.157
 - 45.76.139.124

******************************************************************************
Bifrost Preprod Placebet REST API URL: https://preprod-bifrost-betting-api.bifrost.bet/api/v1/bets/place
Bifrost Preprod Placebet REST API Swagger: https://preprod-bifrost-betting-api.bifrost.bet/swagger-ui/index.html```
i will update once access is whitelisted

---

*Dmytro Rudenko joined the channel* — 4:58 PM

---

**Michael Cheremuhin** — 7:08 PM

@Bhargav please check if you are able to connect to rabbitmq and if https://preprod-bifrost-betting-api.bifrost.bet/swagger-ui/index.html is accessible

---

**Bhargav** — 9:17 PM

We are able to access this from our server. Not from my dev machine. We were able to fetch all the API endpoints by doing curl requests from server.
It's Good to have the access on my machine. But we use VPN.

My current IP is 94.204.92.55. But this could be dynamic.

If you can whitelist the CIDR range:
94.204.88.0/21

> **Thread** (1 replies):
>
> **Michael Cheremuhin** — 10:58 PM
> great! sure @Bhargav , passing to devops team
>

---

**Bhargav** — 10:09 PM

amit@forsyt.io
pmalik@forsyt.io

Please give access to these 2 emails also into this channel.

> **Thread** (2 replies):
>
> **Michael Cheremuhin** — 10:59 PM
> invites sent 
>
> **Bhargav** — 11:19 AM
> @Michael Cheremuhin Can you send invite to amit@forsyt.io again? Amit's previous request to join was rejected.
>

---