Skip to main content
Order returns work analogously to orders in Base and have their own, mirrored block of API methods.

The main method

getOrderReturns downloads returns from Base from a given date, max. 100 per call — the same pagination principle as getOrders.
Unlike orders, there is no confirmed/unconfirmed concept for returns (no date_confirmed) — page through results using date_from (plus the last processed record’s value +1s), or id_from.

Key response fields

Working with statuses and refunds

Tracking changes over time

Just like orders, returns have their own journal: getOrderReturnJournalList — same principle and activation requirement (Profile → API) as getJournalList.

Returns from marketplace channels

For selected marketplace channels, Base can automatically fetch return requests directly from the customer and create returns from them — configurable per sales channel. Once enabled, just monitor new returns as described above.
If you also handle return shipping labels, the principle is the same as for standard shipments — see Shipping labels, just with return_shipment: true.