Automate ShipThis workflows with AI agents that integrate via Open API and EDI

ShipThis overview

ShipThis is headquartered in Newark, Delaware, with a public Tariff page footer listing the address as 200 Continental Drive, Suite 401, Newark, Delaware, 19713. ShipThis describes itself as "an all-in-one platform" / "single integrated solution" with "fully white-labeled digital customer experience Portal and Mobile App." The platform offers 10 integrated modules under a single subscription: operations and shipment lifecycle (air, ocean, land, rail, multimodal), GAAP-compliant accounting, quotation management, tariff and rate management, vendor portal, warehouse management, sales and CRM, customer web and mobile app (white-labeled), eAWB submission, and integrations (REST API, EDI, webhooks).

The pricing model is per-user subscription on the all-modules-bundled package per ShipThis's public pricing page. Per ShipThis: "Shipthis subscription includes access to all modules required for end-to-end freight operations. Our comprehensive package offers a wide range of features and functionalities..." And: "With our per user pricing model, you have the flexibility to pay for precisely what you need." Pricing starts at $89 per user per month per multiple public sources, with add-ons available for specific customer needs. A 30-day free trial is available with no credit card required.

ShipThis describes serving "Mid Size Business, Small Business, Enterprise, Freelance, Nonprofit, Government, and Startup" customer types per public material. ShipThis describes its target customers as "freight forwarders who are looking for an easy to start, easy to use, robust and adoptable solutions without requiring complex implementation costs, IT structure or upfront fees." AI-driven automation features (ShipThis bots, pre-built workflows for shipment lifecycle automation) extend the platform alongside the bundled module suite.

API capabilities and constraints

ShipThis's integration surface is multi-layered. The platform exposes three distinct integration channels that together cover forwarder-side data exchange across the bundled module suite and carrier-side execution.

Layer 1: ShipThis Open API + EDI + webhooks. Forwarder-side reads and writes against ShipThis. Per shipthis.co/features/advance-edi-api-integrations: "Our API uses cutting-edge REST API functionality to deliver resource-oriented URLs that are efficient at exposing the maximum amount of functionality in an easy-to-use interface." EDI and webhook capabilities are also supported per the same page. Specifics including developer portal URL, authentication mechanism, base URL, and sandbox availability are not surfaced clearly in public material; the gap is flagged inline at the end of this section.

Layer 2: Bundled module suite as integration surface. All 10 modules (operations, accounting, quotation, tariff and rate management, vendor portal, warehouse, sales and CRM, customer web and mobile app, eAWB, integrations) accessible via the same Open API + EDI + webhook layer. ShipThis's "single integrated solution" framing means the integration surface is unified across modules. The same API surface handles shipment data, accounting events, quotation data, vendor data, warehouse events, and customer app interactions, rather than separate API surfaces per module.

Layer 3: Carrier-side integration via REST API + EDI + webhooks. ShipThis tracks 100+ airlines and shipping lines per public material. Specific carrier integration mechanism breakdown (which carriers expose APIs that ShipThis uses, INTTRA usage if any, EDI vs REST mix per carrier) is not surfaced clearly in public material; the gap is flagged inline. The hybrid pattern (direct API where carriers expose APIs, EDI or portal automation where carriers haven't published APIs) is structurally similar to other mid-market TMS spokes; specifics for ShipThis are gap-flagged.

For ops automation, this multi-layered architecture means forwarder-side data exchange runs through the unified Open API + EDI + webhook layer across the bundled module suite, while carrier-side execution depends on what each carrier exposes. The integration breadth across the 10-module bundled suite is the technical authority, not single-surface depth.

How Expedion integrates

Expedion agents read shipment state from ShipThis via the REST API, EDI, and webhook surface using forwarder-issued credentials. Booking references, BL drafts, SI fields, container assignments, milestone events, accounting data, and quotation data are pulled against the customer's ShipThis account. The bundled module structure means the same agent layer can read across operations, accounting, customer app, and warehouse data without crossing separate API surfaces.

Agents execute carrier-side workflows through whatever path ShipThis's carrier integration layer uses. Where carriers expose APIs to forwarders (Hapag-Lloyd, ONE, and CMA CGM all publish REST APIs at api-portal.hlag.com, developers.one-line.com, and api-portal.cma-cgm.com), agents work through direct API paths. Where carriers haven't published APIs to forwarders, agents drive each carrier's portal directly. Where carrier-side execution requires portal-specific knowledge (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 handle the variance per workflow.

Completed events write back to ShipThis via REST API, EDI, and webhooks so the system of record stays current across the bundled module suite (operations, accounting, customer app). Authorization is forwarder-provided: agents use customer-supplied ShipThis credentials and carrier-portal credentials with explicit, auditable scope. No credential reuse across forwarder accounts.

Workflows automated on ShipThis

Five Phase 1 workflows on ShipThis. Each row is a workflow; the integration mechanism describes how Expedion agents bridge between ShipThis's REST API + EDI + webhook surface and each carrier's execution channel. ShipThis's bundled module suite handles forwarder-side data exchange across operations, accounting, and customer app under a unified API surface.

Where carrier-side workflows require portal-specific knowledge that the integration layer doesn't fully cover (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 carrier-side execution pattern is hybrid: direct API where carriers expose APIs, portal automation where carriers haven't published APIs.

Onboarding timeline

ShipThis customer onboarding for the TMS itself is described qualitatively in public material as "tailored... based on the requirement discussions. A timeline and plan are then created." ShipThis is a multi-module bundled platform; typical implementation depends on which modules the customer activates beyond the core operations and accounting set. Specifics depend on customer scope and are outside Expedion's surface area.

Expedion onboarding sits on top of an existing ShipThis deployment. The typical engagement runs five to seven business days from kickoff to first agent in supervised production, covering REST API access provisioning, EDI and webhook configuration mapping where applicable, 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 REST API access. The forwarder enables API access for Expedion's agent layer. EDI and webhook configurations are typically already deployed for ShipThis customers using the bundled module suite; agent integration runs against the existing configuration. The 30-day free trial pattern (no credit card required) means forwarders can validate Expedion's value on top of ShipThis without long-term commitment on either side.

Where it fits

ShipThis serves freight forwarders, NVOCCs, customs brokers, and logistics companies of all sizes per public material. Strong fit for small-to-mid forwarders that need a comprehensive module suite (operations, accounting, CRM, warehouse, tariff, customer app) without complex implementation costs or upfront fees per ShipThis's own positioning. Newark, Delaware HQ.

Distinctive elements in the landscape: an all-modules-bundled per-user subscription model. ShipThis describes itself as "an all-in-one platform" / "single integrated solution" with the entire 10-module suite included in the base subscription and add-ons available for specific customer needs. The 30-day free trial with no credit card required is a structural sales-friction-removal feature that fits ShipThis's "easy to start, easy to use, robust and adoptable solutions" positioning. AI-driven automation (ShipThis bots, pre-built workflows for shipment lifecycle automation) extends the platform alongside the core bundled-comprehensiveness foundation.

ShipThis 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 ShipThis or any other TMS the forwarder uses; the agent layer is independent of the TMS choice.

Related pages

Carriers Expedion automates on ShipThis: Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, COSCO, and Evergreen.

Hubs: Carriers hub · Solutions hub · Integrations hub

Solutions on ShipThis: Bill of Lading · Shipping Instructions · Booking · Documentation · Tracking

Other TMS integrations: CargoWise · GoFreight · Magaya · Logi-Sys · Descartes · No TMS

Frequently asked questions