mengantar-apilisted

# Mengantar API: Logistics & Expedition Architecture Use this skill when integrating local Indonesian shipping, courier estimation, and COD (Cash on Delivery) via the Mengantar API aggregator. ## Evidence and Currentness Boundary This is private integration knowledge; no relevant canonical public upstream was found. Endpoint names, account behavior, courier constraints, percentages, and sandbox rules are point-in-time operational claims. Before implementation, compare them with the tenant's current Mengantar documentation/dashboard or support response and one observed sandbox call. Record the environment, account tier, retrieval date, and sanitized evidence. Current provider documentation and observed responses override this file. This skill owns Mengantar-specific routing, COD, wallet, and courier constraints. It does not own storefront behavior, generic order modeling, payment accounting, or courier UI; hand those concerns to their relevant product/domain skills without copying this API contract. ## 1. CORE API TOPOLOGY - **Base URL:** `{BASE_URL}/api/public/{API_KEY}` - **Standard Header:** `Content-Type: application/json`. - **Integrator Header:** If building for WooCommerce, ALWAYS inject `x-client-source: woocommerce`. Without this, orders default to `directCall` and analytics will be skewed. ### Server-Only Credential Boundary Because the credential is embedded in the URL path, every Mengantar request must originate from a trusted backend. Never place the base U