Kalshiseems like there's a delay (up to maybe 10 seconds) before these return. before that I'm getting a 404.
seems like there's a delay (up to maybe 10 seconds) before these return. before that I'm getting a 404.
Byron参与话题 1消息总数 5
该用户的聊天记录定位。
聊天记录
共 5 条，显示第 1-5 条My code just runs automatically, should I be checking the docs all the time for updates? seems like a simple email isn't crazy
My code just runs automatically, should I be checking the docs all the time for updates? seems like a simple email isn't crazy
also, is the get endpoint now failing when you create an order with the new endpoint? I'm getting a 404. e.g. I post with the new create order endpoint, and then try GET /portfolio/orders/{order_id} and GET /portfolio/orders?status=resting and see nothing
also, is the get endpoint now failing when you create an order with the new endpoint? I'm getting a 404. e.g. I post with the new create order endpoint, and then try GET /portfolio/orders/{order_id} and GET /portfolio/orders?status=resting and see nothing
maybe an email? i spent like 2 hours trying to debug the rate limiting because I thought I had introduced a bug somewhere.
maybe an email? i spent like 2 hours trying to debug the rate limiting because I thought I had introduced a bug somewhere.
can we get some kind of notification in the future when these kinds of breaking changes happen? i feel like they keep doing this, just silently push a change and then wait for everyone's code to blow up, I knew nothing about the "v2" order endpoint change until I started getting rate limited while using the old endpoint
can we get some kind of notification in the future when these kinds of breaking changes happen? i feel like they keep doing this, just silently push a change and then wait for everyone's code to blow up, I knew nothing about the "v2" order endpoint change until I started getting rate limited while using the old endpoint