## Overview
/jdy/v2/bd/material belongs to the Cosmic-Star base-data (bd) domain and pages through material (product) master records: number, name, specification, barcode, units, reference cost and sale price. Product master data underpins order, stock and procurement flows — missing code mapping is the number-one cause of integration failure.
### Request essentials
1. Auth per the auth doc: app-token + X-Api-* signing headers + X-GW-Router-Addr.
2. Pagination: page, page_size; common filters: number (code), name (fuzzy), barcode, enable (active flag) and modify_time (incremental cursor).
3. On errcode = 0, data.rows holds the materials. Multi-unit materials expose base/auxiliary conversion rates — normalize quantities to the base unit before syncing.
4. The reverse write is POST /jdy/v2/bd/material; leaving number empty lets Cosmic-Star auto-generate the code, while updates must carry it.
### Typical pipeline
Cosmic-Star materials → Qeasy normalization (code, barcode, category, unit) → creation in Jushuitan/WDT/Weimob; a daily pull validates mapping completeness (marketplace merchant code ↔ Cosmic-Star number) and alerts on unmapped SKUs before order lines fall into manual queues.
### Barcodes and auxiliary attributes
For products with auxiliary attributes (color, size), stock and order lines resolve to attribute combinations, so sync the attribute fields together with the base record. Barcodes may live at product level or per attribute combination — honor the priority between the two layers, or downstream systems receive empty barcodes and scan-based warehousing breaks.