Another unrelated question, is it worth the time to migrate to FIX?
Another unrelated question, is it worth the time to migrate to FIX?
2026-07-16 · Kalshi · 35 条相关讨论
Another unrelated question, is it worth the time to migrate to FIX?
Another unrelated question, is it worth the time to migrate to FIX?
I think the only people who might know the answer to that are not giving away any edge.
I think the only people who might know the answer to that are not giving away any edge.
Is there an improvement in lifecycle latency?
Is there an improvement in lifecycle latency?
I'll infer that means no, there's no improvement
I'll infer that means no, there's no improvement
got it
got it
I certainly do not arrive at the same conclusion.
I certainly do not arrive at the same conclusion.
you have FIX access as non-institutional and low volume?
you have FIX access as non-institutional and low volume?
I am right now wondering if FIX is more reliable for getting events due to the Web Socket feed being flaky lately.
I am right now wondering if FIX is more reliable for getting events due to the Web Socket feed being flaky lately.
some have claimed lower latency via FIX
some have claimed lower latency via FIX
high volume non institutional have FIX access
high volume non institutional have FIX access
premier api tier
premier api tier
yes but low volume part is why it's confusng
yes but low volume part is why it's confusng
rest and fix are processed on different paths on the exchange's side but from what I could measure FIX had lower latency
rest and fix are processed on different paths on the exchange's side but from what I could measure FIX had lower latency
<@351839065919979530> do you mind if I DM you?
<@351839065919979530> do you mind if I DM you?
sure
sure
I'd imagine a big part of it is simply that there's less traffic on FIX. Hence the gatekeeping
I'd imagine a big part of it is simply that there's less traffic on FIX. Hence the gatekeeping
If they gave everyone access to FIX you'd probably start to see similar latencies between that and REST. Just a theory, no way to test it
If they gave everyone access to FIX you'd probably start to see similar latencies between that and REST. Just a theory, no way to test it
They're clearly trying to keep a VIP lane open for the big boys providing the bulk of the liquidity
They're clearly trying to keep a VIP lane open for the big boys providing the bulk of the liquidity
tmk FIX is on a private link which is going to have a more consistent connection pathway. So less p99 spikes
tmk FIX is on a private link which is going to have a more consistent connection pathway. So less p99 spikes
private link is a separate, harder-to-get, benefit than just FIX
private link is a separate, harder-to-get, benefit than just FIX
Did kalshi add the orderbooks stream functional to fix api? I've heard fix had only place order advantage and everyone used default ws.
Did kalshi add the orderbooks stream functional to fix api? I've heard fix had only place order advantage and everyone used default ws.
https://docs.kalshi.com/fix/market-data this is basically a websocket replacement, am i correct ?
https://docs.kalshi.com/fix/market-data this is basically a websocket replacement, am i correct ?
seems like it but i don't think anyone here has FIX access
seems like it but i don't think anyone here has FIX access
are you able to quote rfqs through the rest api or it has to be through fix?
are you able to quote rfqs through the rest api or it has to be through fix?
fix does not give any special access
fix does not give any special access
you can do everything through rest
you can do everything through rest
awesome thank you. gladd to know i don't need fix access to submit bids for rfqs and can do it thourgh the rest api was stressing about it.
awesome thank you. gladd to know i don't need fix access to submit bids for rfqs and can do it thourgh the rest api was stressing about it.
I mean it's well documented in the REST docs, not sure why you'd be stressing it
I mean it's well documented in the REST docs, not sure why you'd be stressing it
i've seen no latency benefit for FIX compared to rest but i might be missing something
i've seen no latency benefit for FIX compared to rest but i might be missing something
I remeasured and I dont have a definitive conclusion that one is faster than the other
I remeasured and I dont have a definitive conclusion that one is faster than the other
At the network level itself, I see that first hop time is shorter for REST (`0.25 ms`) vs FIX (`0.80 ms`). But REST first hop is to ELB, so we don't know how long it has to go from there to Kalshi hosts. And FIX might get you there in one hop. Either way, still sub millisecond at the network itself
At the network level itself, I see that first hop time is shorter for REST (`0.25 ms`) vs FIX (`0.80 ms`). But REST first hop is to ELB, so we don't know how long it has to go from there to Kalshi hosts. And FIX might get you there in one hop. Either way, still sub millisecond at the network itself
I'd guess the Kalshi server performance ends up as the bottleneck if you got this latency sensitive. (speculation)
I'd guess the Kalshi server performance ends up as the bottleneck if you got this latency sensitive. (speculation)
fix has features not present in rest/websocket, such as `CancelOrdersOnDisconnect` (https://docs.kalshi.com/fix/authentication#optional-fields)
fix has features not present in rest/websocket, such as `CancelOrdersOnDisconnect` (https://docs.kalshi.com/fix/authentication#optional-fields)
Yeah I was mostly referring to actual trading operations
Yeah I was mostly referring to actual trading operations
thats true though
thats true though