Изменения

=== Newly changed statuses transfer Get Latest Changed Statuses ===Send To see only latest changed statuses, once in a query while send the request (see the example below). API returns all the orders with recently changed statuses and some other attributes. You save the status information for getting newly each order in your system and confirm the receipt by sending the <code>commitlaststatus</code> request. MeaSoft marks these statuses as received by you and does not return them again. Thus, no matter how many orders is in process, you can get their actual statuses by using only 2 requests. Getting latest changed statuses

<quickstatus>NO</quickstatus> </statusreq>

After successful If the response processing it is necessary processed successfully, use the following request to mark received the returned statuses as successfully received ones sending the following query :

'''Query Fields''' * '''auth''' — Authorization. It is a mandatory element.*'''client''' — indicates whether it is a client or a delivery service partner. It is an optional element. Possible values::*'''CLIENT''' — the default value.:*'''AGENT''' — delivery service partner. Response contains information on the orders tendered for delivery. If successful you will get the following response:

<commitlaststatus> <error error="0" errormsg=">OK"></error></commitlaststatus>

This way of status transfer ensures a complete and correct status transfer even in case if the status has changed in the time period between statuses` query the request and receipt confirmation of their receipt.  If the system hasn`t received the confirmation of a you do not confirm successful status transferreceipt, it the information will consider this information to be not delivered and will display it in case of a requeryreturned again on the next request.

'''Please, note!''' # When this way of data transfer is used (<changes>ONLY_LAST</changes>), the system is reviewing those reviews the orders that have been checked out created for the last 3 months. In case there is an order that has been checked out before this period, then status change for this order won`t get into No information on the list of results of this query executionorders created earlier returns. # The system always returns a the current status, i. e., It means you can get "the NEW" status returned for your the first query request, and "the COMPLETE" status - for your second queryrequest. A dispatch shipment could have gone through several intermediate statuses in between queriesthe request. # The system can never guarantee the order going through a set sequence of statuses successively, i. eis not fixed.For example, you can get "the COMPLETE" status after your first query and "then NEW" status after your second query - such things can happen in case when, for example, the because an operator has mistakenly marked an the order as a completed one by mistake and then corrected his mistakeit.