REST API Create Order Doesn't Set State To Null

Question

question

01928-7325x2 asked Apr 29, '19 Dan commented May 1, '19

REST API Create Order Doesn't Set State To Null

Not sure when this started to changed.
The order API 'create' doesn't set state to null, causing the order available once it created.

Previously, when we create order and adding item, it won't available until we manually set the order state to 'open'. That is expected result, but not sure why suddenly the behavior changed.

Not sure where is the problem, the documentation doesn't mention about any change
https://docs.clover.com/clover-platform/docs/working-with-orders

Orders REST API

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Welcome to the
Clover Developer Community

Answer 1 · 2019-04-30T20:20:05Z

Dan answered Apr 30, '19

Based on looking at /v3/merchants/{merchantId}/orders for POST, as near as I can tell the behavior has not changed, and the state will be set to the state of the order that was sent. Is it possible that you started setting the state before you hit the endpoint?

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 2 · 2019-04-30T21:11:43Z

01928-7325x2 answered Apr 30, '19 Dan commented May 1, '19

@Dan The create order payload is set to empty object.

Previously when we create an order, the online receipt won't available until we set the order state to open.
Now, once the order created the online receipt is available.
And once the order has one item in it, the order will be available in Clover order app.

The case above is no state set to the order.

Did you test and get a different result?

4

10 |2000

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Dan ♦ commented · Apr 30, 2019 at 09:56 PM

I don't know how the online receipts work.

Regarding the order state, if it is not showing up in the Orders app, then the state is probably still null. How are you adding the line item? If you are using the OrderConnector with an android app, then engine is updating the state to OPEN when you add the line item, which is why it is now showing up in the Orders app.

Please provide information on exactly how you are modifying the order, and the state of the order after each operation if you need further assistance.

0 ·

01928-7325x2 Dan ♦ commented · Apr 30, 2019 at 09:59 PM

Just like the title, we are using REST API to create order, adding item and other actions.
When we adding item, no state set until the order has been paid.

0 ·

01928-7325x2 01928-7325x2 commented · Apr 30, 2019 at 10:05 PM

We are going to test again later and let you know the details

0 ·

Dan ♦ commented · May 01, 2019 at 12:06 AM

I did some testing, and at least on our dev server, orders do not appear in the list in web Orders app with a null state normally, but if you search by the uuid (e.g.

ATQSK831NPJXM), then they do appear, and then there is a button for the web receipt and if you follow that it also works. Let me know if this is consistent with what you find.

0 ·

question