## Overview
/jdy/v2/scm/sal_order_list is the Cosmic-Star supply-chain (scm) sales-order list API: a paged GET returning order headers (billno, customer, bill date, amounts, status); entry rows come from the detail endpoint /jdy/v2/scm/sal_order by id.
### Request essentials
1. Auth: exchange an app-token first, then build the X-Api-* headers plus X-GW-Router-Addr per the signing rules (see the auth doc).
2. Pagination: page and page_size (100 or fewer recommended); the total field drives paging.
3. Common filters: bill_no, create_time range, modify_time range (the incremental cursor), bill_status and customer_id.
4. On errcode = 0, data.rows (or data.list by version) holds the orders; normalize currency and tax-inclusive semantics before writing downstream.
### Integration scenarios
- After writing private-domain/dealer orders into Cosmic-Star sales orders (reverse direction: POST /jdy/v2/scm/sal_order), pull them back here for verification.
- Finance: filter approved orders to build the receivables base table.
- Increment on modify_time and use bill_no + entry sequence as the idempotency key into the warehouse.
### Version compatibility
Cosmic-Star has two API generations — this page documents the current jdy/v2 gateway and auth. Legacy integrations on the V1 gateway must re-authorize with app_key/app_secret during migration; old V1 tokens are not portable. Plan a credential cutover window so synchronization does not silently stop when the gateway is switched.