GoFreight overview
GoFreight is a cloud-based freight management platform founded in 2017 by Trenton Chen and Alex Chang. The company is based in the Los Angeles area of California with engineering presence in Taipei, and raised a $23M Series A in November 2022 led by Flex Capital and Headline. Per the company's About page, GoFreight describes itself as "the leading cloud-based freight management platform in North America," serving more than 1,000 freight forwarders and 6,000+ daily users.
GoFreight targets the modern North America mid-market: a cloud-native architecture from 2017 with no XML/SOAP legacy, accounting integrations (QuickBooks, Xero, Sage) built natively, and a public REST API surface published at developers.gofreight.com. Typical customers are freight forwarders and NVOCCs running operations across multiple carriers and trade lanes.
For ops automation, GoFreight's modern REST API surface and active developer portal reduce integration friction at the developer-API layer. The path to value is the same as with any TMS: agents read shipment state, execute carrier-side workflows, and write events back through the API surface, without migrating off GoFreight.
API capabilities and constraints
GoFreight's API is REST/JSON, with the production base URL at api.core.gofreight.co and a public developer portal at developers.gofreight.com. The portal publishes tutorials, API reference, and webhook documentation for the platform's main resource categories: Trade Partners, Ocean Import Master Bills of Lading, Shipment Master Bills, House BL creation, and Container Tracking. A sandbox environment is available on the same base URL through the GoFreight support team.
Authentication uses an API key passed in the X-GATEWAY-TOKEN request header. API key issuance is currently support-mediated: per the developer portal, "GoFreight currently does not allow users to create API keys on their own (but it will be available soon!). You will need to contact GoFreight staff to obtain an API key." Self-serve key creation is on the company's public roadmap as of April 2026 but not yet shipped.
The webhook system supports event subscriptions (for example, invoice.created, invoice.updated, invoice.deleted), HTTP POST callbacks, and HMAC-SHA256 signing via the x-gofreight-signature header. Subscription management is via REST API.
What the API does not cover natively: carrier-specific portal validation rules, including Maersk's HS-code minimum at SI submission, MSC's character sanitisation and ICS2 filing modes on myMSC, and COSCO's portal-specific submission flows. Whether GoFreight's underlying carrier integration uses DCSA T&T v2.2 or carrier-specific patterns is not specified in public-facing material; that gap is flagged inline in Section 4.
How Expedion integrates
Expedion agents read shipment state from GoFreight via the REST API. Booking references, BL drafts, SI fields, container assignments, and milestone events are pulled against the customer's GoFreight account using a forwarder-issued API key passed in the X-GATEWAY-TOKEN header. Reads are scoped to the data the customer authorizes and do not cross account boundaries.
Agents execute carrier-side workflows on each carrier's canonical channel. On Maersk, MSC, CMA CGM, ONE, COSCO, and Evergreen this means authenticated portal sessions on Maersk.com, myMSC, My CMA CGM, ONE eCommerce, SynCon Hub, and ShipmentLink, where the carrier's portal is the canonical execution surface and where carrier-specific rules apply. On Hapag-Lloyd, CMA CGM, and ONE, agents use carrier-published REST APIs (api-portal.hlag.com, api-portal.cma-cgm.com, developers.one-line.com) where production-grade endpoints exist.
Completed events write back to GoFreight via REST API so the system of record stays current. Where appropriate (for example, a new shipment ready for SI submission), agents subscribe to GoFreight webhook events so activation is event-driven rather than polling-based, reducing latency and API quota usage. Authorization is forwarder-provided: agents use customer-supplied GoFreight API keys and carrier-portal credentials with explicit, auditable scope. No credential reuse across forwarder accounts.
Workflows automated on GoFreight
Five Phase 1 workflows on GoFreight. Each row is a workflow; the integration mechanism describes how Expedion agents bridge between GoFreight's REST API and each carrier's execution channel. GoFreight's platform overview explicitly names integration with Maersk, MSC, CMA CGM, and COSCO; broader carrier coverage falls under the company's 125+ carrier integration count.
GoFreight's REST API handles forwarder-side message exchange consistently across all five workflows. The Container Tracking API specifically aggregates ocean carrier, terminal, and rail data with EDI 315 format support into a single API surface, abstracting per-carrier integration variance from the forwarder. Where carrier-side execution requires portal-specific knowledge (Maersk's HS-code enforcement, MSC's ICS2 filing options, COSCO's lack of confirmed DCSA conformance, and similar per-carrier nuances on the broader 125+ carrier surface), Expedion agents handle the variance per workflow. The integration depth on GoFreight itself is uniform, modern, and webhook-event-driven where the use case warrants it.
| Workflow | GoFreight integration | Carrier execution | Coverage |
|---|---|---|---|
| Booking | REST API: create/read booking records, webhook events for booking lifecycle | Carrier portal or API for the four named carriers (Maersk.com, myMSC, My CMA CGM, SynCon Hub) plus the broader 125+ ocean carrier coverage; portal-only for spot products (Maersk Spot, CMA CGM SpotOn) | Full |
| Shipping Instructions | REST API: SI field exchange via shipment master bill endpoints | Carrier portal SI submission with carrier-specific validation (Maersk HS-code enforcement, MSC character rules and ICS2 filing modes on myMSC) | Full |
| Bill of Lading | REST API: House BL creation, draft BL events | Carrier portal amendment and telex release flows for the four named carriers; eBL platform integration not specified in GoFreight's public material | Full |
| Documentation | REST API: document attachment, customs documentation coordination (ISF filing, AMS connectivity per platform overview) | Carrier portal VGM, DG declarations, and advance manifest filings (AMS, ACI, ICS2) per the four named carriers and the broader 125+ carrier surface | Full |
| Tracking | Unified Container Tracking API aggregating ocean carrier, terminal, and rail feeds; supports EDI 315 format for tracking data; underlying carrier integration pattern (DCSA T&T v2.2 vs proprietary feeds) not specified in public material | 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
GoFreight customer onboarding for the TMS itself follows a typical mid-market platform pattern. GoFreight's published Platform Overview describes a four-to-eight week range covering setup, data migration, user training, and go-live for mid-market deployments. Specifics depend on customer scope, accounting-integration complexity (QuickBooks, Xero, Sage), and the size of the rollout, and are outside Expedion's surface area.
Expedion onboarding sits on top of an existing GoFreight deployment. The typical engagement runs five to seven business days from kickoff to first agent in supervised production, covering API key provisioning, webhook subscription setup, 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 the API key. Per Section 2, the forwarder requests an API key from GoFreight's support team during customer onboarding; once issued, Expedion uses the customer's key with explicit, auditable scope. Self-serve key creation is on GoFreight's public roadmap as of April 2026 but not yet shipped; the support-mediated path is the current production model.
Where it fits
GoFreight competes in the modern mid-market North America TMS segment, serving freight forwarders and NVOCCs that need a cloud-native platform with strong accounting integration and a usable browser UI. Customers typically run GoFreight as the operational system of record across booking, SI, BL, documentation, customs filing, and accounting workflows.
Distinctive elements in the landscape: a 2017-founded greenfield codebase, a public REST API and webhook system with sandbox access, native QuickBooks, Xero, and Sage integrations built into the platform, and per-user pricing per the company's published Platform Overview.
GoFreight is one of several TMS choices a forwarder can make; that choice is an operational decision driven by company size, accounting needs, and team workflow. Expedion runs on top of GoFreight or any other TMS the forwarder uses; the agent layer is independent of the TMS choice.
Related pages
Carriers Expedion automates on GoFreight: Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, COSCO, and Evergreen.
Hubs: Carriers hub · Solutions hub · Integrations hub
Solutions on GoFreight: Bill of Lading · Shipping Instructions · Booking · Documentation · Tracking
Other TMS integrations: CargoWise · Magaya · Logi-Sys · Descartes · ShipThis · No TMS
Frequently asked questions
Does Expedion replace GoFreight?
No. Expedion runs on top of GoFreight as the agent execution layer. GoFreight stays the system of record; agents read from GoFreight via REST API, execute carrier-side workflows on each carrier's portal or API, and write completed events back. Webhook subscriptions enable event-driven activation. There is no data migration, no replatforming, and no parallel TMS to maintain.
How does Expedion authenticate to GoFreight?
Via a forwarder-issued API key passed in the X-GATEWAY-TOKEN header. The forwarder requests an API key from GoFreight's support team during onboarding (self-serve key creation is on GoFreight's public roadmap but not yet shipped as of April 2026). Expedion uses the customer's API key with explicit authorization and scope; no credential sharing across forwarder accounts.
What does GoFreight's webhook system give us?
HMAC-SHA256-signed event subscriptions for invoice and shipment events. Where webhooks are appropriate (for example, a new shipment ready for SI submission), agent activation is event-driven rather than polling-based, which reduces latency and API quota consumption. Subscription management is via REST API, with HTTP POST callbacks signed in the x-gofreight-signature header.
Does GoFreight support DCSA T&T v2.2 directly?
GoFreight's public Container Tracking API aggregates carrier, terminal, and rail data into a unified surface and supports the EDI 315 format for tracking data. Whether the underlying carrier integration uses DCSA T&T v2.2 directly or carrier-specific feeds is not specified in public-facing material. For forwarders that require DCSA-conformance audit trails for regulatory or compliance reasons, Expedion agents can poll carrier DCSA APIs directly in parallel where conformance is verified (6 of 7 Tier 1 carriers).
Will Expedion integration work for forwarders running GoFreight alongside other systems?
Yes. GoFreight's REST API is the integration surface for the agent layer; if forwarders run additional systems (accounting platforms like QuickBooks, Xero, or Sage natively integrated into GoFreight, or external systems), the agent layer reads from GoFreight without disrupting the existing integration topology. Most agent-driven activity is reads and writes against existing GoFreight records, not new external connections.