Getting order(s) is not returning "expire_time"

Exchange/Pro API
,
#1

Hello! I am trying to use the REST API to get info on orders. The API reference states that a potential output is expire_time “at which order expires.” I assume that this is for GTT limit orders where you can specify the cancel_after as a min, hour, and day, and then expire_time translate that to a timestamp.

To test this, I created a day-long order to sell at some random price well above the current “ask” on the sandbox. When getting the order in the REST API, the following is returned (censoring the UUIDs):

id                  ########-####-####-####-############
client_oid          ########-####-####-####-############
price               47300.00000000
size                0.00119000
product_id          BTC-USD
profile_id          ########-####-####-####-############
side                sell
type                limit
time_in_force       GTT
post_only           True
created_at          2022-04-02T01:23:23.329167Z
fill_fees           0.0000000000000000
filled_size         0.00000000
executed_value      0.0000000000000000
status              open
settled             False

Note that the time_in_force is GTT, but expire_time is not specified.

Is this a bug? Am I misunderstanding something?

#2

Minor update: I am getting expire_time when creating an order, just not when getting an existing order (either a single order or all orders).

#3

Hello @Magi! We already raised this issue to the responsible team of specialists and we will get back to you once we have more details. Thanks for reaching out!

3 Likes
#4

Just wondering if there are any updates on this. It looks like the info is still not being returned:

Creating order to sell 0.000838 BTC for 33792.25 USD...
Time: 2022-04-13T16:27:12.885617
FROM CREATING ORDER:
{'price': '33792.25', 'size': '0.000838', 'expire_time': '2022-04-13T16:28:13.009Z', 'time_in_force': 'GTT', 'post_only': False}
FROM GETTING INFO:
{'price': '33792.25000000', 'size': '0.00083800', 'time_in_force': 'GTT', 'post_only': False}
#5

Hi @Magi, we noted that you were able to extract the expire_time from your initial Create Order response. We were able to replicate this in the Sandbox as well. We believe that this is the only viable option to satisfy your workflow as of this moment.

In the meantime, our engineers are still checking to see whether this is a documentation issue or an API response issue. We’ll update you as soon as possible.

Thank you for your patience and understanding!

2 Likes
#6

Hi @Magi, Thank you for your patience. We would like to inform you that this bug has been now resolved, expire_time should now be getting returned for GTT Limit orders when calling an existing order.

2 Likes