<@624575779023355904> why does this endpoint: https://clob.polymarket.com/data/order/ORDER_ID
return a field of ``` "created_at": 1700000000``` in epoch seconds? is it possible you guys can make these ms timestamps? We need more precesion.. i think it should be pretty easy to do as well
<@624575779023355904> why does this endpoint: https://clob.polymarket.com/data/order/ORDER_ID
return a field of ``` "created_at": 1700000000``` in epoch seconds? is it possible you guys can make these ms timestamps? We need more precesion.. i think it should be pretty easy to do as well
from docs: https://docs.polymarket.com/api-reference/trade/get-single-order-by-id
from docs: https://docs.polymarket.com/api-reference/trade/get-single-order-by-id
is this something you guys can do please?
is this something you guys can do please?
why do you need that?
why do you need that?
just better for data/logging purposes
just better for data/logging purposes
but they show as the same thing
but they show as the same thing
i mean you can log/store it yourself as well
i mean you can log/store it yourself as well
never seen anybody complain about this
never seen anybody complain about this
I do log it myself
I do log it myself
can look into it
can look into it
thank you, would be nice to have ms precision, it should just be quick "fix"
thank you, would be nice to have ms precision, it should just be quick "fix"
If considered, please make this a separate field for migration purposes. People may use the timestamps to cancel older orders (definitely not me though)
If considered, please make this a separate field for migration purposes. People may use the timestamps to cancel older orders (definitely not me though)
yeah of course
yeah of course
just looking into the best way we can surface it - definitely don't want any breaking changes
just looking into the best way we can surface it - definitely don't want any breaking changes
im not saying change timestamp, just add 3 more sig figs of accuracy to them yk
im not saying change timestamp, just add 3 more sig figs of accuracy to them yk
int->float is a breaking change too
int->float is a breaking change too
ah alright, but doesnt even need to be float, can still stay int just 13 long instead of 10
ah alright, but doesnt even need to be float, can still stay int just 13 long instead of 10
that's a breaking change too
that's a breaking change too
oh really
oh really
Yeah, arguably even more nasty since the program wont automatically catch it by throwing a parsing error
Yeah, arguably even more nasty since the program wont automatically catch it by throwing a parsing error
true lol i get u
true lol i get u
but ye anyways, idc how its added, i just would like more precision.having seconds is horrible.. like thats insanely bad accuracy in this realm
but ye anyways, idc how its added, i just would like more precision.having seconds is horrible.. like thats insanely bad accuracy in this realm