There seems to be a bug in case of sorting order_by in Draft order APIs.
I have tried to access the order API with the following URL and it is working perfectly:
But when I try to access with the same parameters with the draft order API, it only shows the result in ascending order.
Does anyone face the same issue with Draft Order API?
As an undocumented filtration method on both (from what I can tell) the order and draft order endpoints, it's not going to be guaranteed to work.
If you're filtering by created_at, I would suggest instead using since_id. Not only will it accomplish effectively what you want to achieve, but it will also be more performant.
Have you found a solution?
Thank you for the quick response.
As far as I know the since_id parameter will also result me the draft orders in ascending order but my requirement is to dislpay latest order first. You have any work around here?