Orders

Lists the orders in which your store is the supplier — the ones you received to fulfill —, from newest to oldest, with pagination and filters.

Returns the full order: values, customer, payments, deliveries with products, and the status history.

Moves the order to the next status in the fulfillment flow and saves, along with it, the data that status requires — the order number in your ERP, the invoice (nota fiscal), the tracking code.

Lists the products of the order whose delivery lead time is under inquiry and has not yet been filled in. It is the queue of items that depend on you informing the lead time before the order moves on.

Reports the preparation lead time for the items left with lead time on request. This submission is what releases the order for payment: once the lead times are answered, the customer is notified that the order is available.

Attaches the XML of the invoice (nota fiscal) to the order. The request body is the file itself, sent as binary content — the raw stream of the bytes of the.xml. It is not multipart/form-data, there is no form field and the XML does not go inside a JSON.

Reports, item by item, the status of each product in the order — what has already shipped, what is being prepared, what is pending. This is the tracking the customer sees during fulfillment.

Returns the item tracking saved on the order — the active set.

Deletes the tracking of the order's items, entirely — all parts, all statuses. The order goes back to having no tracking at all.

Lists the orders originated in your store — those your customers placed, including those that will be fulfilled by other partners —, from newest to oldest, with pagination and filters.

Returns the full details of an order originated in your store: values, customer, payments, deliveries with products, and the status history.

Lists the partner orders that originated from the same customer order. An order with items from different suppliers is split into one partner order per supplier, and that split is what this route returns.

Allows the originating store to move an order that was created there to the next status, saving along with it the data that status requires.

Allows the originating store to attach the invoice (nota fiscal) XML to an order that was created there. The request body is the file itself, sent as binary content — the raw byte stream of the.xml. It is not multipart/form-data, there is no form field, and the XML does not go inside a JSON.

Allows the originating store to report, item by item, the status of each product in an order that originated in it.

Returns the tracking of the items of an order originated in your store — the active set.

Deletes, in full, the item tracking of an order originated in your store.