What is the current status of the XML API vs REST API?
Please note that from the end of February the XML Order API will be shut off so we encourage you to migrate to the REST API as soon as possible if you still haven't done it.
You can contact us for any question you may have for this process.
Related Articles
What is the significance of the "WAITING_PAYMENT" status?
The "WAITING_PAYMENT" status is related to the order processing cycle. However, as of now, the "WAITING_PAYMENT" status is not available in the Orders API (REST).
Are there any limitations on API requests?
Yes, to prevent abusive usage, requests to the API might be limited to 200 per hour and per IP address. If this limit is reached, the API will return an HTTP status code 429, indicating "Too Many Requests."
Can I check the status of the update for each SKU after making a request using the "update_offers" endpoint?
Yes, the request_id returned in the 207 Multi-Status response can be used as a parameter for a GET request. This allows you to check the status of the update for each SKU, providing more insight into the processing of your request.
Can I filter orders based on the date they were last updated?
Yes, you can filter orders based on their status update dates using the parameters status_updated_at_start and status_updated_at_end.
What parameters are required to use the "Get Orders" endpoint?
To use the "Get Orders" endpoint, you must include the following required parameters: seller_contract_id: The contract ID for the seller. order_reference: The order reference. status: The order status (e.g., PENDING). carrier: The carrier for the ...