Chanmama E-Commerce Data Query

Problem

Working with Chanmama data APIs is usually not a single lookup. It requires auth setup, resolving names to IDs, choosing the primary entity, assembling query fields, and interpreting results. Passing an author, product, or shop name as an ID, or summing values like 1000W+ as exact numbers, leads to incorrect conclusions.

How It Works

• Permission and version checks: call permission/list first to verify CMM_API_KEY, membership tier, available modules, and data windows before querying restricted endpoints.
• Entity resolution: when only names are available, use common search to obtain author_id, promotion_id, shop_id, brand_code, or aweme_id.
• Reference selection: choose the right reference file based on the primary entity, such as product.md, author.md, shop.md, brand.md, live.md, video.md, or category.md.
• Query execution: build api and query from the documented fields, call the request runner scripts/call_cmm_api.py, and surface msg when code != 0.
• Metric interpretation: keep sales and volume values as raw interval strings. Compare them qualitatively only; do not perform addition, subtraction, multiplication, or division.

Boundaries

Data is usually T+1, so the end date for “last 7 days” should be yesterday. Leaderboards, period totals, audience profiles, and detail fields depend on membership rights. Platform values are interval-based and should not be used for precise financial aggregation.