Malformed Error Response on Customer Cart Endpoint

46 views
Skip to first unread message

chris.lucas

unread,
Mar 29, 2018, 4:11:23 PM3/29/18
to deliverydotcom API V2
Hello,

We've run into an issue where we're getting an error response from the Custom Cart endpoint that does not match the error format described here.

When attempting to POST a customer cart to a merchant that does not exist, we receive this response:

{
    "code": "no_rest",
    "user_msg": "Merchant not found.",
    "dev_msg": "Merchant not found."
}

(It should also be noted that this response had a status code of 200, which I believe is in error.)

According to the documentation for customer checkout, we should be receiving an response along the lines of this:

{
  "message": [
    {
      "code": "no_rest",
      "user_msg": "Merchant not found.",
      "dev_msg": "Merchant not found."
    }
  ]
}

With a status code of 400 to denote a bad user request.

- Chris Lucas

deliverydotcom API V2

unread,
Mar 29, 2018, 4:34:58 PM3/29/18
to deliverydotcom API V2
Sorry, you are experiencing this issue.  We will looking into and get back you.

deliverydotcom API V2

unread,
Mar 29, 2018, 8:44:06 PM3/29/18
to deliverydotcom API V2


Hi Chris,

Checking the endpoint, what was documented is accurate.  See below:

Customer Cart POST


Customer Checkout POST



Can you provide the request body?  So I can better diagnose.  Leave out the client id.


Thanks.



chris.lucas

unread,
Mar 30, 2018, 9:02:24 AM3/30/18
to deliverydotcom API V2
I believe reference the wrong endpoint, If you try hitting https://api.delivery.com/customer/cart/432 (no body necessary; though a valid Authorization header is required), you'll get a response as shown in the screenshot below.


- Chris Lucas

deliverydotcom API V2

unread,
Apr 2, 2018, 3:18:26 PM4/2/18
to deliverydotcom API V2
Thanks for the clarification.  We have found the issue and will post a fix Thursday evening.

- Lawren

chris.lucas

unread,
Apr 2, 2018, 5:33:59 PM4/2/18
to deliverydotcom API V2
That's great to hear. Thanks for the quick response.

- Chris

deliverydotcom API V2

unread,
Apr 6, 2018, 12:30:16 PM4/6/18
to deliverydotcom API V2
Hi chris.lucas,

The release has been delayed until Monday.  I will update this thread once it is released.  Sorry for the inconvenience.

- Lawren

chris.lucas

unread,
Apr 6, 2018, 12:43:07 PM4/6/18
to deliverydotcom API V2
Hi Lawren,

No worries. I appreciate the status update.

- Chris

deliverydotcom API V2

unread,
Apr 10, 2018, 11:59:52 AM4/10/18
to deliverydotcom API V2
Hi chris.lucas,

The fix has been released.  As usual, if you have any problems let us know.

- Lawren
Reply all
Reply to author
Forward
0 new messages