## Overview
This endpoint belongs to the YonBIP sales cloud (sd domain) and returns sales orders page by page. It is invoked with POST plus a JSON body, while the access_token travels in the URL query string. A typical use case: after a dealer portal or e-commerce mid-office writes sales orders into YonBIP, finance and supply-chain systems pull order status, amounts and fulfillment progress back through this API for reconciliation and tracking.
### Request essentials
1. Put access_token in the URL; set Content-Type: application/json.
2. pageIndex (1-based) and pageSize (recommended at or below 100) control pagination; use pageCount or totalElements in the response to decide when to stop.
3. Filters are passed via the condition object — by bill date, voucher state or customer code; the exact condition fields depend on the tenant's YonBIP version, so confirm against the tenant-scoped API docs.
4. For incremental sync, drive the cursor from the order modify/approve time and overlap the window by 5-10 minutes to avoid boundary losses.
### Fields
The data array carries order code, customer, vouchdate, taxRate, origMoney, origTaxMoney and orderDetails rows (product, quantity, taxUnitPrice). Mind currency and tax-inclusive vs tax-exclusive semantics before posting amounts into finance systems.
### Operational tips
Keep the request id of every page in the integration logs — YonBIP support will ask for it when investigating data gaps. When the same order appears in overlapping windows, deduplicate on the order id rather than the order code, because codes can be reissued in rare correction flows. Finally, confirm the tenant's number-format settings before parsing amounts into decimals.