Magaya overview
Magaya is headquartered in Miami, Florida and led by CEO Gary Nemmers. Per the April 2026 Coneksion partnership press release, Magaya describes itself as "the leading freight management platform for freight forwarders and customs brokers," with native modules spanning the supply chain stack: forwarding workflow, warehouse management (Magaya WMS), customs filing (ACELYNK), rate management (Catapult, now branded Magaya Rate Management), customer portal (Qwyk), freight marketplace (SimpliShip), and iPaaS (Magaya Connect, post-Omniboom).
The architecture is a roll-up across acquisitions. Catapult was acquired in September 2020 and integrated as Magaya Rate Management. Omniboom was acquired in September 2024 and integrated as Magaya Connect. Qwyk, SimpliShip, and ACELYNK were absorbed across the same window. The result is a forwarder-focused platform with native warehouse, customs, and rates that few peer platforms in this market segment match.
Mid-market Americas positioning. Strong fit for freight forwarders and customs brokers that need integrated WMS plus customs plus rate management alongside core forwarding workflow. In April 2026, Magaya announced an expansion of ocean carrier connectivity through a partnership with Coneksion, building on the existing INTTRA partnership for ocean carrier bookings and shipping instructions.
API capabilities and constraints
Magaya's integration surface is multi-layered. The platform exposes four distinct integration channels that together cover forwarder-side data exchange and carrier-side execution.
Layer 1: Magaya Open API. Forwarder-side reads and writes against the core platform: quotes, shipments, invoices, warehouse receipts, customs filings, and rate records. Per Magaya, the Open API "offers comprehensive web services compatible with popular programming languages." Specifics including developer portal URL, authentication mechanism, base URL, and sandbox availability are not surfaced in public material; the gap is flagged inline at the end of this section.
Layer 2: Magaya Connect. Built on the September 2024 Omniboom acquisition, Magaya Connect is a hybrid message and event-bus integration platform with pre-built connectors and webhook subscriptions. Per Magaya, "Magaya Connect facilitates transitioning from one application to another through eventual migration. Magaya Connect enables modern event-based communication among an organization's applications through a hybrid message/event bus model." Pre-built connectors target popular cloud and on-premise applications including logistics, ERP, CRM, accounting, and e-commerce platforms (Shopify, WooCommerce, Magento, Salesforce Commerce Cloud).
Layer 3: INTTRA partnership for ocean carrier bookings and shipping instructions. Per magaya.com/carrier-connections: "The INTTRA and Magaya connection provides the opportunity to send bookings to ocean carriers and receive shipping instructions directly in your Magaya system." Magaya customers can access "more than 60 leading carriers and NVOCCs through the INTTRA platform." INTTRA, now part of e2open, provides EDI-grade carrier integration via INTTRA's IFTMIN, IFTSTA, and IFTMBF message types at the EDI layer.
Layer 4: Coneksion partnership for expanded ocean carrier connectivity. In April 2026, Magaya announced an expansion of ocean carrier connectivity through a partnership with Coneksion (Helsinki-based), described as "a leading provider of fully managed data connectivity solutions for global logistics and supply chains" built on "the Coneksion Common Carrier Layer (CCL) and a proprietary iPaaS." Per Magaya CEO Gary Nemmers in the announcement, the expansion "delivers connectivity in a way that is scalable and easy to adopt, helping our customers manage ocean shipments more effectively within the solutions they already rely on."
For ops automation, this multi-layered architecture means forwarder-side data exchange runs through the Open API and Magaya Connect surfaces, while carrier-side execution runs through the INTTRA partnership with the April 2026 Coneksion expansion announcement extending the connectivity surface. The integration breadth is the load-bearing technical authority.
How Expedion integrates
Expedion agents read shipment state from Magaya via the Open API. Booking references, BL drafts, SI fields, container assignments, and milestone events are pulled against the customer's Magaya account using forwarder-issued credentials. Where Magaya Connect webhook subscriptions are configured for the customer's deployment, agent activation can be event-driven rather than polling-based.
Agents execute carrier-side workflows through the Magaya integration topology. For ocean carriers, this means INTTRA-mediated booking submission and shipping-instruction exchange per Magaya's existing carrier-connections architecture, with the April 2026 Coneksion partnership announcement expanding the connectivity surface. Where partnership coverage does not reach (Maersk's HS-code enforcement at SI submission, MSC's character validation and ICS2 filing modes on myMSC, COSCO's portal-only flows for Chinese-origin documentation), Expedion agents drive each carrier's portal directly and write the result back through Magaya's Open API.
Completed events write back to Magaya via the Open API and Magaya Connect so the system of record stays current. Authorization is forwarder-provided: agents use customer-supplied Magaya credentials and carrier-portal credentials with explicit, auditable scope. No credential reuse across forwarder accounts.
Workflows automated on Magaya
Five Phase 1 workflows on Magaya. Each row is a workflow; the integration mechanism describes how Expedion agents bridge between Magaya's Open API + Magaya Connect surface and each carrier's execution channel. Magaya's ocean carrier connectivity runs through the INTTRA partnership (more than 60 leading carriers and NVOCCs per magaya.com/carrier-connections) and the April 2026 Coneksion partnership announcement expanding this connectivity layer.
Magaya's ocean carrier connectivity runs through the INTTRA partnership for booking and SI exchange, with the April 2026 Coneksion partnership announcement expanding this connectivity layer. Forwarder-side data exchange runs through the Open API and Magaya Connect surface, which is consistent and event-bus-capable. Where partnership coverage does not reach (Maersk's HS-code enforcement at SI submission, MSC's character validation and ICS2 filing options, COSCO's lack of confirmed DCSA conformance), Expedion agents handle the variance per workflow. The agent layer sits between Magaya and each carrier's portal where the partnership layer does not fully extend.
| Workflow | Magaya integration | Carrier execution | Coverage |
|---|---|---|---|
| Booking | Open API: create/read booking records. Magaya Connect webhook events for booking lifecycle | INTTRA-mediated booking submission to ocean carriers per Magaya carrier-connections architecture; Coneksion Common Carrier Layer expanding coverage from April 2026; portal-only fallback for spot products (Maersk Spot, CMA CGM SpotOn, GreenX) | Full |
| Shipping Instructions | Open API + Magaya Connect: SI field exchange against shipment records | INTTRA partnership receives shipping instructions directly into Magaya per the carrier-connections page; carrier-portal fallback for ICS2 filing modes (F10, F11, F12/F13, F14/F15/F17), MSC character validation, Maersk HS enforcement | Full |
| Bill of Lading | Open API: House BL creation, draft BL events | Carrier portal amendment and telex release flows; eBL platform integration (WAVE BL, iQAX, GSBN, Bolero) NOT specified in Magaya public material | Full |
| Documentation | Open API + Magaya Connect: document attachment, customs documentation. ACELYNK acquisition provides ACE-certified ABI-software customs filing | Carrier portal VGM, DG declarations, advance manifest filings (AMS, ACI, ICS2). Magaya's native ACELYNK integration handles US ACE/ABI customs filing alongside carrier-side declarations | Full |
| Tracking | Magaya tracks containers across more than 100 sealines per magaya.com/platform; underlying integration pattern (DCSA T&T v2.2 direct, INTTRA pass-through, or independent aggregator) not publicly specified | DCSA T&T API per carrier (v2.2 on 6 of 7 Tier 1; COSCO via SynCon Hub plus third-party aggregators) | Full |
Onboarding timeline
Magaya implementation timelines for the TMS itself are not surfaced in primary sources. Magaya is a multi-module platform spanning Magaya Supply Chain, Magaya WMS, Magaya Rate Management, Magaya Customs Compliance (ACELYNK), and Magaya Digital Freight Portal (Qwyk); typical implementation depends on which modules the customer activates and the data-migration scope from existing systems. Specifics are outside Expedion's surface area.
Expedion onboarding sits on top of an existing Magaya deployment. The typical engagement runs five to seven business days from kickoff to first agent in supervised production, covering Open API access provisioning, Magaya Connect webhook subscription setup where appropriate, customer-specific custom-field reconciliation, carrier credential provisioning, and a supervised validation period across booking, SI, BL, documentation, and tracking workflows on the carriers in scope.
The first onboarding step is Open API access. The forwarder enables Open API access for Expedion's agent layer and configures any Magaya Connect webhook subscriptions for event-driven activation. Customs filing via ACELYNK and rate management via Catapult and Magaya Rate Management are typically already deployed for Magaya customers; agent integration with these modules is part of the same onboarding window.
Where it fits
Magaya competes in the mid-market Americas TMS segment, serving freight forwarders and customs brokers that need native warehouse management, customs filing, and rate management alongside core forwarding workflow. The Miami headquarters reflects long-standing Latin America and Caribbean trade-lane focus alongside US freight forwarders and NVOCCs.
Distinctive elements in the landscape: a roll-up-of-acquisitions architecture across the supply chain stack. Magaya WMS provides native warehouse management built into the platform. ACELYNK delivers ACE-certified ABI-software customs filing. Catapult and Magaya Rate Management handle freight rate quoting and management natively. Magaya Connect, derived from the Omniboom acquisition, provides iPaaS-grade integration to e-commerce, ERP, and CRM systems. The combination of forwarder workflow plus warehouse plus customs plus rates plus iPaaS in a single platform is rare in this market segment.
Magaya is one of several TMS choices a forwarder can make; that choice is an operational decision driven by company size, module needs, trade-lane focus, and team workflow. Expedion runs on top of Magaya or any other TMS the forwarder uses; the agent layer is independent of the TMS choice.
Related pages
Carriers Expedion automates on Magaya: Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, COSCO, and Evergreen.
Hubs: Carriers hub · Solutions hub · Integrations hub
Solutions on Magaya: Bill of Lading · Shipping Instructions · Booking · Documentation · Tracking
Other TMS integrations: CargoWise · GoFreight · Logi-Sys · Descartes · ShipThis · No TMS
Frequently asked questions
Does Expedion replace Magaya?
No. Expedion runs on top of Magaya as the agent execution layer. Magaya stays the system of record; agents read from Magaya via Open API and Magaya Connect, execute carrier-side workflows through the INTTRA + Coneksion partnership layers and direct carrier portals where partnership coverage does not extend, and write events back. There is no data migration, no replatforming, and no parallel TMS to maintain.
How does Expedion handle Magaya's INTTRA + Coneksion partnership architecture?
Agents use the partnership layers where they cover the workflow: booking submission and SI exchange via INTTRA per Magaya's carrier-connections architecture, plus the Coneksion Common Carrier Layer per the April 2026 expansion announcement. Where partnership coverage does not reach (carrier-specific portal validation rules, ICS2 filing modes, spot-product portal flows, COSCO's lack of confirmed DCSA conformance), agents drive the carrier portal directly and write the result back through Magaya's Open API.
What about Magaya's other modules (Rate Management, WMS, Customs Compliance)?
Agents work with the standard Magaya forwarding workflow first (booking, SI, BL, documentation, tracking). Where the customer has Catapult or Magaya Rate Management deployed, agents can read rate data for quoting context. Magaya WMS warehouse events surface through Magaya Connect and can feed agent workflows. ACELYNK customs filing via ACE/ABI is typically handled by the customer's customs team, but Expedion can read filing status as part of the documentation workflow.
Will Expedion integration affect our Magaya pricing?
Magaya's pricing is not surfaced in this spoke's source material. Most agent-driven activity is reads and writes against existing Magaya records via Open API; pricing implications depend on the customer's Magaya contract. Confirm with the Magaya account team during onboarding.
Does Magaya use DCSA T&T v2.2 for tracking?
Magaya's public material describes ocean shipment tracking across 'more than 100 sealines' but does not specify whether the underlying pattern uses DCSA T&T v2.2 directly, INTTRA pass-through, or an independent aggregator. For compliance-sensitive forwarders requiring DCSA-conformance audit trails, Expedion agents can poll carrier DCSA APIs directly in parallel where conformance is verified (6 of 7 Tier 1 carriers).