Magaya API
Magaya is an integrated logistics platform powering freight forwarding, customs compliance, warehouse management, and rate management for freight forwarders, customs brokers, and 3PLs. An unofficial API lets you programmatically pull shipments, warehouse receipts, invoices, quotes, and tracking events—and push updates like new bookings, cargo releases, and accounting transactions back into Magaya Supply Chain.
What is Magaya?
Magaya is an integrated logistics software platform that helps freight forwarders, customs brokers, and 3PLs streamline shipping, warehousing, and compliance operations. Customers run end-to-end freight forwarding, NVOCC, customs brokerage, warehouse/3PL, rate management, and accounting workflows on Magaya Supply Chain, and extend their stack through Magaya Connect and the Magaya Open API framework.
Core product families:
- Magaya Supply Chain (freight forwarding, transportation, tracking, and accounting)
- Magaya WMS (receiving, inventory, picking, packing, and billing)
- Magaya Customs Compliance (ACE-certified ABI filings and denied party screening)
- Magaya Rate Management (rate search, quoting, tariff filing, and RFQ management)
- Magaya Digital Freight Portal (branded customer portal for quotes, booking, and shipment visibility)
- Magaya Connect (iPaaS integration layer with pre-built connectors, webhooks, and the Open API)
Common data entities:
- Shipments, Bookings, Pickup Orders, Bills of Lading
- Warehouse Receipts, Cargo Releases, Inventory Items, Pick/Pack Lists
- Quotations, Rates, Tariffs, RFQs
- Invoices, Bills, Payments, Accounting Transactions
- Customs Filings, ABI/ACE Entries, Denied Party Screening Results
- Tracking Events, Carrier Connections, Container and Air Status
The Magaya Integration Challenge
Forwarders and 3PLs run mission-critical operations on Magaya daily, but turning its portal- and desktop-driven workflows into API-driven automation is non-trivial:
- XML Web Service legacy: The Magaya Open API is exposed as an XML Web Service against the Magaya Communication Suite, requiring XSD-driven message handling rather than simple REST
- Per-tenant configuration: Each forwarder configures the Communication Suite to accept incoming messages, so generic integrations break across deployments
- Cloud and on-premise spread: Magaya runs in both cloud and on-prem models, each with different network and authentication setups
- Module-by-module coverage: Supply Chain, WMS, Customs Compliance, and Rate Management each have their own object models and lifecycle states
- Partner connector gates: Many flows route through Magaya Connect and pre-built connectors, requiring setup before programmatic access
- Compliance-sensitive data: Customs filings, ABI/ACE entries, and denied party screening require precise handling and audit trails
How Supergood Creates Magaya APIs
Supergood reverse-engineers authenticated Magaya sessions, the Communication Suite XML Web Service, and Magaya Connect interactions to deliver a resilient, normalized API layer for your Magaya deployment—across Supply Chain, WMS, Customs, and Rate Management.
- Handles username/password and MFA securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes XML Web Service responses into consistent JSON objects across shipments, warehouse receipts, quotes, and invoices
- Aligns with your Communication Suite configuration, modules, and entitlements for compliant access
Use Magaya with AI agents: Magaya MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, deployment model, and authentication setup.
- Supergood Generates and Validates Your API
We deliver a production-ready Magaya adapter tailored to your Communication Suite configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Magaya evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Magaya deployment using username/password, or MFA, and obtain a session token for downstream calls.
Shipments
/shipmentsList shipments, bookings, and bills of lading with filters for status, mode, customer, and date range.
Shipments
/create_shipmentCreate a new shipment or booking and add it to Magaya Supply Chain against your configured workflow.
Warehouse
/warehouse_receiptsRetrieve warehouse receipts, inventory items, and cargo release status from Magaya WMS.
Rates
/quotesPull quotations, rates, and tariffs from Magaya Rate Management with origin, destination, and service filters.
Accounting
/invoicesRetrieve invoices, bills, and accounting transactions, including related shipping information, for reconciliation.
Use Cases
Sync shipment and tracking data into your warehouse
- Pull active shipments, bookings, and bills of lading from Magaya Supply Chain into a single warehouse - Stream tracking events, container and air status to downstream visibility and BI tools - Reconcile customer and consignee records across modules for unified reporting
Automate booking and order intake
- Push customer sales orders and bookings into Magaya Supply Chain automatically - Validate shipment and party details against your Communication Suite configuration - Route confirmations and exceptions back to customers without portal clicks
Reconcile invoices and accounting transactions
- Sync invoices, bills, and payments from Magaya into general ledger and AR systems - Match accounting transactions to their related shipments and warehouse receipts - Surface unbilled charges and overdue accounts to finance workflows
Power rate quoting and customs workflows
- Pull rates and tariffs from Magaya Rate Management for instant quote generation - Trigger denied party screening and ABI/ACE customs filings on new shipments - Attach compliance results and documents to the shipment record
Technical Specifications
Authentication
Username/password and MFA handled in a managed session against the Magaya Communication Suite
Connectivity
Authenticated sessions plus the Magaya Open API XML Web Service surfaced through Magaya Connect where exposed
Response format
Normalized JSON across shipments, warehouse receipts, quotes, invoices, and customs objects
Rate limits
Adaptive throttling tuned to your deployment to avoid Communication Suite-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for shipments, tracking, and invoices with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for shipment status, warehouse receipt, cargo release, and invoice changes
Latency
Sub-second reads on cached entities; multi-second writes when posting shipments and accounting transactions
Throughput
Horizontally scaled workers sized to freight forwarding and 3PL transaction volume
Reliability
Retry, backoff, and idempotency keys for bookings, cargo releases, and accounting transactions
Adaptation
Continuous monitoring of Magaya releases, Connect connector changes, and per-tenant configuration drift
Frequently asked questions
Yes. Supergood normalizes data across Magaya Supply Chain, WMS, Customs Compliance, and Rate Management, so shipments, warehouse receipts, quotes, and invoices are available through one consistent API surface.
No. Supergood works with your existing Magaya deployment and authenticated sessions. Magaya Connect connectors are only required when you specifically want to route through the iPaaS layer.
The Open API is an XML Web Service requiring XSD-driven message handling and Communication Suite configuration. Supergood wraps that surface—plus authenticated session flows—into a normalized JSON API so you integrate once without managing XML schemas.
Yes. Supergood adapts to either deployment model, operating against the same authenticated surfaces with network configuration tuned to your environment.
Yes. Customs filings, ABI/ACE entries, and denied party screening results are exposed through the normalized API and can be attached to the related shipment records.