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 order (e.g., UPS).

created_at_start: The lower bound for order creation date.

created_at_end: The upper bound for order creation date.

Related Articles
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.
How can I unfreeze offers using the "unfreeze_offers" endpoint?
How can I unfreeze offers using the "unfreeze_offers" endpoint?
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.
Are there any limitations for the "update_offers" endpoint?
Quotas: 200 requests allowed per hour per IP address. HTTP status code 429 (Too Many Requests) will be returned if the limit is reached. Payload Size: The maximum payload size for the PATCH request body is 5 MB
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).

Related Articles