API CHANGES?

I opened a ticket with this information - is ANYONE else having these kinds of issues??

We are seeing recently where the API is not returning entityID's properly but is returning -1 in the fields. We are seeing this with about 50% of the orders recently we have been getting.

Here are a couple of examples:
Order from August 17 at 9:48pm - the order looks fine in the system but from our end when we pull the API data it returns a -1 as the entityID - its not happening with every order but is happening frequently, very much causing headaches and hassles with our off site reporting.

Another example is:
The API sent us order ID 3459227 - but we never got an email about it nor can we find it in the system but yet its in our API output from BC but returns a -1 as the entityID
Online Shop 16-Aug-2013 08:17 PM

We see this order in our API output but not in the BC system - why is this? Why all of the sudden is the API not stable. We need stability because we use the API for accounting purposes.
Here are some other order examples that are not in BC front end but show up in the API but also return -1 as the entityID
Online Shop 16-Aug-2013 05:36 PM - order id: 3459160
Online Shop 16-Aug-2013 05:17 PM - order id: 3459148
Online Shop 16-Aug-2013 04:17 PM - 3459108

I have literally dozens of these "messed up api returns" in our off site db....

We need answers and resolution, if the system is no longer stable then that poses a huge problem for our business.....

Here is a raw API output -

GRRRR!

According to our database of orders we have kept for over a year the bad data did not start coming through until around May 30th 2013 - all the orders before then are fine, orders after then are coming through about half of them with the entity ID as -1

This would still be tied to a user would it not with an entity ID?  :-)

My other thing is why we do not see this before May 28th or there abouts as well.

That would be cool if it turned out to the be the case but the status id's being also returned in this case are showing the order was completed. If I am correct that is what   [statusTypeId] => 749177 means.?

Tom

[statusTypeId] => 749177   is our default for "purchased payment received" - 

And all of the -1 entityID's are listing this status. I think this is what has us freaked out a bit is why would an abandoned cart carry a status of "purchase - payment received" if the order was not completed and cart abandoned.

Just trying to understand Liam - we have a pretty intricate off bc system tied to this API which generates accounting data -

We were coding some of our software and in our reports we were seeing huge gaps in the output - where as certain distributors (our resellers) were not showing up at all in our reports(known distributors), so when we query our DB we get nothing (e.g. name not found) but we see all these orders with -1 entity ID but with a purchase payment received status -

We found it because our system dumps all the orders and all the customers into different DB tables, we then use break away tables to pull together certain data - e.g. name with entityID - we KNOW these "names" have placed orders but they do not show up in our breakaway tables - so we dug into the db and discovered all the -1's in the fields. We had never seen this before and have had this system hooked into the API for over a year, doing as much as 100k a month in sales.

It was not until our reports starting not showing over half of the distributors we realized an issue (distributors come and go, so to see it varying a little was not unusual) -

So I still have concern something isn't right but will check further into the theory you have above Liam and sincerely appreciate the feedback on it 

Thanks everyone for clearing it up... I just had never seen it before in our previous dumps I guess - but i understand fully - peace.

Tom