{"section":"announcements","requestedLocale":"en","requestedSlug":"2018-12-28-get-order-and-list-orders-apis-may-now-return-orders-with-the-null-status","locale":"en","slug":"2018-12-28-get-order-and-list-orders-apis-may-now-return-orders-with-the-null-status","path":"docs/en/announcements/2018/december/2018-12-28-get-order-and-list-orders-apis-may-now-return-orders-with-the-null-status.md","branch":"main","content":"As of __January 30, 2019__, requests to the [Get Order](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders/-orderId-) and [List Orders](https://developers.vtex.com/docs/api-reference/orders-api#get-/api/oms/pvt/orders) APIs may return orders with the `null` status. That result wasn’t previously available while using the referred APIs.\n\n\n## Main advantages\nThe new status allows order closing, even when the Workflow is facing stability issues. Before that change, the Workflow (our order status management system) would impact the checkout system, preventing orders to be closed properly. Now, orders are closed as they're supposed to, and get the null status until the incident is resolved.\n\nIn other words, __the new status is responsible for the Workflow's optimization and makes the order closing process more stable__.\n\n\n## What you need to do\nYou must review all your store’s integrations that use the Get Order and List Orders (like ERP integrations, for example). __The ones that, for any reason, are not ready to receive the new response must be adjusted before January 30.__"}