Vendor Return API

sblackwsblackw Posts: 4Member

BGSU has an interface that extract purchase orders and vendor returns information and then updates the a few fields in Lightspeed Retail.  The process has been successfully running for more than a year.  The request starting failing around October 23rd.  Below is the API request and current results.

Did something change with this endpoint?  Are there any plans to fix this issue?

Thanks,
Scott

https://api.merchantos.com/API/Account/147027/VendorReturn/310.xml


Body of the request<?xml version='1.0'?><VendorReturn><Note><note>TEST</note></Note><status>done</status></VendorReturn>

We are now getting a 405 response. 
<?xml version="1.0"?>
<Error>

    <httpCode>405</httpCode>
    <httpMessage>Method Not Allowed</httpMessage>
    <message>The requested resource does not allow that action.</message>
    <errorClass>Exception</errorClass>
</Error>

 

6 comments

  • gregaricangregarican  Posts: 311Member 
    I tested it out and was able to GET a VendorReturn, but not able to PUT an update to the same record. Didn't see anything listed in the online API documentation but this --> https://developers.lightspeedhq.com/retail/endpoints/DisplayTemplate-VendorReturn/#get-single-venderreturn. Which involves pulling info, as opposed to pushing info. Seems to be either under-documented or otherwise modified?
  • gregaricangregarican  Posts: 311Member 
    If you trace the HTTP 405 response, you will see in the response header that this endpoint appears to only support GET. Not PUT, POST, etc. Guess that explains that :neutral:

    HTTP/1.1 405 Method Not Allowed
    Date: Mon, 29 Oct 2018 15:07:39 GMT
    Content-Type: application/json
    Content-Length: 141
    Connection: close
    x-frame-options: SAMEORIGIN
    X-XSS-Protection: 1; mode=block
    X-Content-Type-Options: nosniff
    X-LS-Acct-Id: 164019
    X-LS-OAuth-Client-Id: 64577
    X-LS-API-Bucket-Level: 10/100
    X-LS-Shard-Id: 18
    X-LS-API-Drip-Rate: 5
    Allow: GET
    X-LS-Master-System: true
    X-LS-Master-Account: true
    X-LS-Master-Catalog: false
    Vary: Accept-Encoding
    Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
    Server: cloudflare
    CF-RAY: 47168d93ac235606-ORD

    {"httpCode":"405","httpMessage":"Method Not Allowed","message":"The requested resource does not allow that action.","errorClass":"Exception"}
  • sblackwsblackw Posts: 4Member

    So apparently Lightspeed Retail removed the unofficial API functionality.  How do I go about requesting this functionality to be implemented?

    Scott

  • gregaricangregarican  Posts: 311Member 
    If I were you I'd post it under http://ideas.lightspeedretail.com. The only official place for API support is this message board, and if you don't see anything fed back here then I'd post it as an idea.

    Although if it was an undocumented API function that wasn't officially supported, then you unfortunately were building something that wasn't guaranteed to be there for the long haul. :neutral:
  • sblackwsblackw Posts: 4Member
    The undocumented API was the best option for integrating.  No option exists now.  Thanks for providing the ideas link.
  • gregaricangregarican  Posts: 311Member 
    Now that I'm a couple years into API integrations and working with these various providers, I've found a sadly common theme. Mainly API deprecation and changes without adequate prior notice. In this case it wasn't documented to begin with, but I've run into other cases where the carpet is yanked from under me with production breaks. Shopify being case in point quite a few times this year...
Sign In or Register to comment.