Are ppl still getting 400 errors on rfqs?
Are ppl still getting 400 errors on rfqs?
2026-06-23 · Kalshi · 77 条相关讨论
Are ppl still getting 400 errors on rfqs?
Are ppl still getting 400 errors on rfqs?
yup i still am
yup i still am
Same here. every RFQ has returned 400 invalid_parameters (midland) since ~3:14 ET on 6/19, same body that worked for months. One data point that might explain it: I tried the FIX RFQ market-maker session (KalshiRFQ) and it rejects with '58=API usage level is not allowed for FIX'. My account is on the advanced tier. Are these rfq quotes requiring Market-Maker / Premier access to quote?? or is this a bug? If it's now an access requirement, can a non-Premier account request access?
Same here. every RFQ has returned 400 invalid_parameters (midland) since ~3:14 ET on 6/19, same body that worked for months. One data point that might explain it: I tried the FIX RFQ market-maker session (KalshiRFQ) and it rejects with '58=API usage level is not allowed for FIX'. My account is on the advanced tier. Are these rfq quotes requiring Market-Maker / Premier access to quote?? or is this a bug? If it's now an access requirement, can a non-Premier account request access?
no ive been getting same behavior as you since 6/19 as well
no ive been getting same behavior as you since 6/19 as well
I haven’t changed anything in weeks so I don’t think there was any sort of breaking API change. I am on advanced FWIW
I haven’t changed anything in weeks so I don’t think there was any sort of breaking API change. I am on advanced FWIW
<@229623186310955008> Does your payload look different than this? I also tried rounding to 4 decimals with no luck. `{"rfq_id": "rfq_id_xyz", "yes_bid": "0.000", "no_bid": "0.871", "rest_remainder": false}`
<@229623186310955008> Does your payload look different than this? I also tried rounding to 4 decimals with no luck. `{"rfq_id": "rfq_id_xyz", "yes_bid": "0.000", "no_bid": "0.871", "rest_remainder": false}`
I read through these openapi docs (https://docs.kalshi.com/openapi.yaml) as well for the POST Quote endpoint and I really can't see anything in the docs that is pointing towards a user error. Really starting to think it could just be an undocumented change or bug
I read through these openapi docs (https://docs.kalshi.com/openapi.yaml) as well for the POST Quote endpoint and I really can't see anything in the docs that is pointing towards a user error. Really starting to think it could just be an undocumented change or bug
```POST https://api.elections.kalshi.com/trade-api/v2/communications/quotes headers: KALSHI-ACCESS-KEY, KALSHI-ACCESS-SIGNATURE, KALSHI-ACCESS-TIMESTAMP, accept: application/json, content-type: application/json body: {"rfq_id":"<uuid>","yes_bid":"0.0000","no_bid":"0.6479","rest_remainder":false}``` ```Response: 400 {"error":{"code":"invalid_parameters","message":"invalid parameters","service":"midland"}}``` I saw in the docs that 400 can often come from Price not on a valid step, or RFQ already closed. but i validated the rfq still open before and after my attempt to create quote and have tried with differnt percision for the step lead but nothing has solved this for me
```POST https://api.elections.kalshi.com/trade-api/v2/communications/quotes headers: KALSHI-ACCESS-KEY, KALSHI-ACCESS-SIGNATURE, KALSHI-ACCESS-TIMESTAMP, accept: application/json, content-type: application/json body: {"rfq_id":"<uuid>","yes_bid":"0.0000","no_bid":"0.6479","rest_remainder":false}``` ```Response: 400 {"error":{"code":"invalid_parameters","message":"invalid parameters","service":"midland"}}``` I saw in the docs that 400 can often come from Price not on a valid step, or RFQ already closed. but i validated the rfq still open before and after my attempt to create quote and have tried with differnt percision for the step lead but nothing has solved this for me
Same here. I tried changing types for most of these too (strs to floats, booleans to strs, etc) I am hoping this could prompt the Kalshi engineers to surface slightly more detailed error messages as well. If we could get more details than "invalid parameters" we would be able to troubleshoot much quicker
Same here. I tried changing types for most of these too (strs to floats, booleans to strs, etc) I am hoping this could prompt the Kalshi engineers to surface slightly more detailed error messages as well. If we could get more details than "invalid parameters" we would be able to troubleshoot much quicker
<@540172766909956096> <@550528091244724224> there have been a handful of us in here asking for some assistance on this. They said they were aware of it but thats all we’ve heard. Did your 400 errors also start on 6/19 around 19:14 UTC? That seems to be a common timestamp for people who were quoting RFQs fine and then all of the sudden 100% response of 400 errors
<@540172766909956096> <@550528091244724224> there have been a handful of us in here asking for some assistance on this. They said they were aware of it but thats all we’ve heard. Did your 400 errors also start on 6/19 around 19:14 UTC? That seems to be a common timestamp for people who were quoting RFQs fine and then all of the sudden 100% response of 400 errors
at exactly that time <@872238471593492520> ...
at exactly that time <@872238471593492520> ...
Same with me
Same with me
Not sure if that’s reassuring or worse lol but seems to be affecting some accounts and not others so hopefully we can get some help now that it’s not the weekend
Not sure if that’s reassuring or worse lol but seems to be affecting some accounts and not others so hopefully we can get some help now that it’s not the weekend
Agree. Would love to see an example payload from one of the accounts that are able to get quotes through... otherwise it doesn't seem like there is anything we can do
Agree. Would love to see an example payload from one of the accounts that are able to get quotes through... otherwise it doesn't seem like there is anything we can do
<@540172766909956096> <@872238471593492520> <@550528091244724224> They said they did a sweeping permaban wave for quoters who had too low of a fill rate and are wasting system resources, gl
<@540172766909956096> <@872238471593492520> <@550528091244724224> They said they did a sweeping permaban wave for quoters who had too low of a fill rate and are wasting system resources, gl
i worry he isnt trolling, i ran same underlying code on my wifes acct and i get a 201 instead of 400
i worry he isnt trolling, i ran same underlying code on my wifes acct and i get a 201 instead of 400
But surely they would inform people
But surely they would inform people
So unless you can point me to an official post im assuming its false
So unless you can point me to an official post im assuming its false
I don’t think anyone is trying to be rude <@1259011052063031408> , it is just very surprising that they would do this without a warning
I don’t think anyone is trying to be rude <@1259011052063031408> , it is just very surprising that they would do this without a warning
The silence on the topic from the devs seems to kind of confirm the theory, but doing something like that without warning and permanently seems absurd.
The silence on the topic from the devs seems to kind of confirm the theory, but doing something like that without warning and permanently seems absurd.