Commands not working


#1

Been using the following for months without any issues:
https://apiverson.ordoro.com/order?limit=100&status=awaiting_fulfillment&sales_channel=xxx

Sometime yesterday, started getting 'status is not recognized as a internal or external command.

Did something change?


#2

Hi,

I’m not sure what happened. Nothing has changed on our end. Just used the same url sans the sales_channel bit, and received a proper order response.

If this persists, please send the response so we can try and dig into it.


#3

It still persists. We’ve been using this URL for several months (with the sales_channel) without any issues. We parse in orders differently based off the sales_channel ID and need it to work the way it did yesterday.


#4

Trying different things out. This works
https://apiverson.ordoro.com/order?sales_channel=xxx
but this doesn’t
https://apiverson.ordoro.com/order?sales_channel=xxx&offset=100

It appears that it is not accepting more than one command per request.


#5

Hi Dan,

Nothing has changed on our end regarding this api.

I am able to run the full request via curl https://apiverson.ordoro.com/order?status=awaiting_fulfillment&sales_channel=xxx&limit=1 without issue.

Do you have a response you can send? What language are you using?


#6

/order?status=awaiting_fulfillment&sales_channel=xxx&limit=1
works for me as well.

Could you please try
/order?sales_channel=xxx&offset=100

For troubleshooting this, I’m using cURL for Windows


#7

All querystring arguments are being received as expected
Nothing has been changed on the API side.


#8

Figured out what was wrong with curl…I needed some quotes around the command. So now on to our actual issue which is with a ZappySys SSIS plugin.

Its saying that the underlying connection was closed. Received an unexpected EOF

Have there been any changes to SSL or TLS?


#9

No, we had some networking related issues for a couple of hours on the 21st, but this has since been resolved. Are you still running into this EOF problem?


#10

Sill having EOF issues, but appears to be with the method we’re using to download the files. Working on an alternative method that appears to be working. Thanks.