i mean i agree with you this would be absolutly wild, i was just not expecting it to work on her account either...
i mean i agree with you this would be absolutly wild, i was just not expecting it to work on her account either...
该用户的聊天记录定位。
i mean i agree with you this would be absolutly wild, i was just not expecting it to work on her account either...
i mean i agree with you this would be absolutly wild, i was just not expecting it to work on her account either...
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
where did you see this?
where did you see this?
at exactly that time <@872238471593492520> ...
at exactly that time <@872238471593492520> ...
```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
yeah idk what that dudes takking about
yeah idk what that dudes takking about
ive read the docs brother, doesnt mean that i can instantly find the solution to my bug. take the stick up out of ur ass for once geez
ive read the docs brother, doesnt mean that i can instantly find the solution to my bug. take the stick up out of ur ass for once geez
damn... came to this server to try to get some help and pointers, guess that was prob asking too much
damn... came to this server to try to get some help and pointers, guess that was prob asking too much
maybe i missed it could u link this doc?
maybe i missed it could u link this doc?
Tried this too no luck
Tried this too no luck
i havent changed anything either is the odd thing. all a sudden on june 19 some new change seemenly went live
i havent changed anything either is the odd thing. all a sudden on june 19 some new change seemenly went live
would you mind sharing your req body? trying to figure out what im doing wrong
would you mind sharing your req body? trying to figure out what im doing wrong
is anyone here successfully quoting combo RFQs over REST right now?
is anyone here successfully quoting combo RFQs over REST right now?
noted thanks
noted thanks
so you need to be premier now to quote rfqs?
so you need to be premier now to quote rfqs?
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?