Veeqo Order API - 500 Internal server Error

I encountered 500 Internal server error repeatedly while calling Order Endpoint

Request:- GET
API Endpoint:- https://api.veeqo.com/orders
Header:- API KEY

Response:-
{“status”:“500”,“error”:“Internal Server Error”}


Hi techosunny,

Please can you try going to https://app.veeqo.com/orders to see if it loads, then try changing the URL to https://api.veeqo.com/orders. This will test whether you can access the API using your browser cookies.

Let me know what happens when you do that then I can investigate further.

Thanks,

Hey Phil,

https://app.veeqo.com/orders
Yes, I’m able to access this one.

https://api.veeqo.com/orders
Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details.

Thanks,

This looks like its a cache error. I’m afraid we’re going to need a bit more time to investigate this. I’ll get back to you as soon I have a solution.

Do you able to share what kind of cache error you are facing right now…?

Its just a timeout error which doesn’t really tell us anything unfortunately.

I’ve just reactivated your Tech2Peak - Developer account for another month if you need to test on another account.

Thanks,

My developer account working fine but please fix this soon…

Hey,

Just had another look at this and, there is something a bit odd at work here. We’re going to have another look at it tomorrow morning. As a work around at the moment this query works https://api.veeqo.com/orders?since_id=13376004&status=awaiting_fulfillment which returns the most recent 199 orders from that account.

Its a big query and takes close to a minute to load all the data, but it gets there. I’ll get back to you tomorrow, hopefully with some more information.

@techosunny We have a fix that should be deployed overnight tonight. In the mean time please can you specify the page param in your request.
E.G. send the GET request to https://api.veeqo.com/orders?page=1

Sure, I’ll specify page param in my request…
Thanks

The fix for this should be deployed now.

Thanks Phil… :slight_smile: