ApparelMagic API
ApparelMagic is a cloud ERP, PLM, and CRM platform built exclusively for fashion brands to run design, inventory, wholesale and retail orders, manufacturing, and accounting in one system. An unofficial API lets you programmatically pull orders, products, inventory, customers, purchase orders, shipments, and invoices—and push updates like new orders, style records, and production data back into ApparelMagic.
What is ApparelMagic?
ApparelMagic is a cloud-based ERP, PLM, and CRM platform designed exclusively for fashion and apparel brands to manage operations from design through delivery. Brands use ApparelMagic to develop styles, manage inventory across multiple warehouses and channels, process wholesale and retail orders, run B2B eCommerce, control manufacturing timelines and vendor relationships, and access financial reporting—all in a single system connected to ecommerce, shipping, and accounting tools.
Core product areas include:
- PLM (style development, line sheets, tech packs, costing)
- Inventory Management across multiple warehouses and channels
- Sales & Order Management (wholesale and retail)
- B2B eCommerce and Line Sheets
- Manufacturing & Production with a Vendor Portal
- Logistics & Fulfillment
- Accounting & Financial Reports
Common data entities:
- Products, Product Attributes, Size Ranges, SKU Warehouse
- Orders, Order Items, Customers, Salespeople, Terms
- Purchase Orders, Vendors, Receivers, Pick Tickets
- Inventory, Warehouses, Locations, Divisions
- Shipments, Ship Methods, Shipping Terms, Return Authorizations
- Payments, Credit Memos, Chart of Accounts, Currencies
The ApparelMagic Integration Challenge
Fashion brands run their entire operation on ApparelMagic, but turning that data into reliable API-driven automation is non-trivial:
- Enterprise-gated API: Programmatic API access is offered on the Enterprise plan, so lower tiers must work through pre-built connectors or request access from sales
- Per-tenant subdomain endpoints: Each shop's API lives at its own company.app.apparelmagic.com/api/json host, so integrations must be configured per account
- Token management: Access depends on per-shop tokens generated in settings, plus warehouse and vendor names that vary by tenant
- Matrixed apparel data: Styles explode into size/color SKUs across size ranges and warehouses, so naive integrations miss the underlying variant model
- Coverage variability: Endpoint depth differs across orders, production, inventory, and accounting objects, and not every workflow is exposed identically
- Multi-channel reconciliation: Wholesale, retail, and B2B eCommerce orders flow through the same system but need consistent IDs and status handling downstream
- Production and fulfillment workflows: Purchase orders, receivers, pick tickets, and shipments require careful sequencing and document handling
How Supergood Creates ApparelMagic APIs
Supergood reverse-engineers authenticated sessions and ApparelMagic's JSON API surface to deliver a resilient API layer for your ApparelMagic shop—across PLM, orders, inventory, production, and accounting.
- Handles token-based authentication against your per-shop subdomain and credential rotation securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Products, Orders, Inventory, Purchase Orders, Shipments, and Accounting so you integrate once and rely on consistent objects
- Preserves the style/size/color SKU matrix and per-warehouse inventory so variant-level data stays intact
Use ApparelMagic with AI agents: ApparelMagic MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, channels, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready ApparelMagic adapter tailored to your shop configuration and data entities.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as ApparelMagic evolves.
API Endpoints
Authentication
/authenticateAuthenticate to your ApparelMagic shop using a per-account token against your company subdomain JSON endpoint and obtain a session for downstream calls.
Products
/productsList styles and products with their size ranges, attributes, and per-warehouse SKU details.
Orders
/ordersRetrieve wholesale and retail orders with order items, customers, salespeople, and status filters.
Orders
/create_orderCreate a new order with line items, customer, terms, and ship method against your shop configuration.
Inventory
/inventoryPull on-hand and available inventory across warehouses and locations at the SKU and size level.
Purchasing
/purchase_ordersList purchase orders, vendors, and receivers to track production and inbound fulfillment.
Fulfillment
/shipmentsRetrieve shipments, pick tickets, ship methods, and return authorizations with tracking details.
Use Cases
Sync orders and inventory across channels
- Pull wholesale, retail, and B2B eCommerce orders with line items into a single warehouse - Stream SKU- and size-level inventory across warehouses to downstream planning tools - Reconcile customer and salesperson records across channels for unified reporting
Automate purchasing and production workflows
- Push purchase orders to vendors and pull receiver records back as production lands - Track style costing and tech-pack data from PLM into downstream costing tools - Trigger reorder and production events when inventory falls below thresholds
Streamline fulfillment and shipping
- Sync pick tickets and shipments with tracking into your OMS or 3PL - Reconcile ship methods, shipping terms, and return authorizations downstream - Surface delayed or partial shipments to customer-service workflows
Reconcile billing and accounting
- Sync invoices, payments, and credit memos into your general ledger and AR systems - Match orders and shipments against chart-of-accounts entries and currencies - Surface outstanding balances and terms to finance reporting
Technical Specifications
Authentication
Per-shop API token against your company.app.apparelmagic.com subdomain, handled in a managed session
Connectivity
Authenticated sessions plus ApparelMagic's /api/json endpoint surfaced where exposed on your plan
Response format
Normalized JSON across Products, Orders, Inventory, Purchasing, Fulfillment, and Accounting objects
Rate limits
Adaptive throttling tuned to your shop to avoid ApparelMagic-side limits
Session management
Automatic session refresh, token replay handling, and credential rotation
Data freshness
Near real-time pulls for orders, inventory, and shipments with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order creation, shipment, inventory change, and purchase-order updates
Latency
Sub-second reads on cached entities; multi-second writes when posting orders and purchase orders
Throughput
Horizontally scaled workers sized to multi-warehouse, multi-channel order and SKU volume
Reliability
Retry, backoff, and idempotency keys for order, shipment, and purchase-order writes
Adaptation
Continuous monitoring of ApparelMagic releases and per-shop configuration drift
Frequently asked questions
ApparelMagic offers direct API access on its Enterprise plan. Supergood works against your authenticated ApparelMagic shop and its JSON surface, so you get a consistent API layer regardless of which connectors your plan exposes.
Supergood preserves ApparelMagic's variant model—styles expand into size and color SKUs across size ranges and warehouses—so you get variant-level products and inventory rather than a flattened catalog.
Yes. Wholesale, retail, and B2B eCommerce orders are normalized into a single order surface with consistent customer, item, and status fields, so you integrate once across channels.
Yes. Purchase orders, vendors, receivers, and pick tickets are exposed through the same normalized surface, so production and inbound fulfillment data sits alongside orders and inventory.
Each ApparelMagic shop has its own subdomain endpoint and API token. Supergood manages token-based authentication, session refresh, and credential rotation per shop so headless automation stays reliable.