MercuryGate API
MercuryGate is a multimodal transportation management system (now part of Infios Transportation Management) used by shippers, brokers, 3PLs, and carriers. This page is an independent design exercise that asks what a well-designed MercuryGate API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed MercuryGate API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing MercuryGate product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is MercuryGate?
MercuryGate is a multimodal transportation management system (now part of Infios Transportation Management) used by shippers, brokers, 3PLs, and carriers. The platform spans planning, execution, visibility, and settlement - covering load planning, rate and contract management, dispatch and tendering, freight execution across modes, and freight audit, payment, and claims. Customers use MercuryGate to optimize routing, exchange data with trading partners over EDI and APIs, manage carrier portal interactions, and reconcile invoices and claims at scale.
Core product areas include:
- Transportation Management & Planning (e.g., orders, loads, optimization, multi-stop and multi-mode routing)
- Rate & Contract Management (e.g., contracts, lanes, accessorials, fuel surcharges, rating engines)
- Dispatch & Tendering (e.g., carrier selection, EDI 204/990, spot quotes, capacity assignment)
- Visibility & Collaboration (e.g., status events, EDI 214, carrier portal updates, ETAs, documents)
- Freight Settlement (e.g., freight bill audit, payment, cost allocation, claims management)
- Business Intelligence & Reporting (e.g., spend analytics, on-time performance, carrier scorecards)
An API for a platform like this would naturally organize around its core data entities:
- Companies (shippers, consignees, bill-to, carriers), Users, Roles, and Permissions
- Orders & Loads (references, modes, equipment, statuses, division/agent codes)
- Stops & Appointments (pickup/delivery windows, locations, dock/door)
- Carriers & Capacity (SCAC, contracts, lanes, qualifications, insurance)
- Rates & Tariffs (contract rates, spot quotes, accessorials, fuel)
- Tracking Events & Documents (status, geolocation, BOL/POD, exceptions)
- EDI Transactions (204 tender, 990 response, 214 status, 210 invoice, 997 ack)
- Invoices, Settlements, and Claims (audit results, accruals, payment terms, claim records)
The MercuryGate Integration Challenge
Shippers, brokers, 3PLs, and carriers rely on MercuryGate to run their freight networks, but turning a sprawling TMS into reliable API automation is non-trivial:
- Product breadth: Planning, execution, visibility, and settlement span distinct suites with different objects, statuses, and lifecycles that must be reconciled into a single integration
- EDI-driven flows: Tenders, status updates, and invoices often arrive as batched EDI (204/990/214/210); polling and event capture require careful orchestration to achieve real-time behavior
- Carrier portal data: Updates submitted by drivers and carriers via portal screens (status, documents, appointment changes) are spread across views and may not surface uniformly through standard endpoints
- Module/licensing gates: Coverage of rating, settlement, claims, and BI varies by purchased modules and customer tier, making uniform API access tricky
- Tenant variability: Custom fields, workflows, division/agent codes, and partner-specific rating logic differ by customer, complicating one-size-fits-all integrations
- Authentication & permissions: MFA plus role-based controls and agent/division scoping complicate headless, unattended automation
- Settlement rigor: Freight audit, cost allocation, and claim postings have strict business rules; incorrect updates can break downstream payment and accruals
What a MercuryGate API Could Look Like
If MercuryGate exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like MercuryGate: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate against MercuryGate (Infios) with credentials and MFA; returns a session token
Shipments
/shipmentsWould list shipments with stops, status, equipment, mode, and division/agent scoping
Shipments
/create_shipmentWould create a new shipment or load, including stops, references, equipment, and accessorials
Rates
/ratesWould retrieve contract rates, spot quotes, accessorials, and fuel surcharges for a lane and equipment
Visibility
/trackingWould pull EDI 214 status events, geolocation, ETAs, and exceptions for active shipments
Dispatch
/create_loadWould create a load and tender to a carrier or carrier group with contract or spot rate selection
Use Cases
Automated Shipment Creation and Tendering
- Push orders and loads into MercuryGate from OMS, ERP, or planning systems - Auto-tender to carriers using contract rates and lane rules - Capture EDI 990 tender responses and reroute on rejection
Programmatic Rate Quote Retrieval
- Query contract rates, spot quotes, accessorials, and fuel surcharges - Compare carrier options across modes for a given lane and equipment - Surface least-cost or best-fit carrier selections in upstream apps
EDI 204/214 Ingestion and Status Sync
- Receive and parse EDI 204 tenders and 214 status messages at scale - Normalize stop events, geolocation, and ETAs into a unified shipment timeline - Push status events into customer portals, 3PL dashboards, and BI
Freight Settlement and Invoice Reconciliation
- Pull EDI 210 invoices and freight audit results for accruals - Match invoices to load cost, accessorials, and fuel surcharges - Post payment status, claim records, and exceptions back into MercuryGate
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require username/password 2.0 and MFA (SMS, email, TOTP) handled per-tenant
Connectivity
Would build on REST API plus EDI feeds (204/990/214/210/997) over AS2/SFTP/VAN
Response format
JSON for REST endpoints; X12 EDI envelopes normalized to JSON for downstream consumers
Rate limits
Adaptive throttling tuned to your tenant's MercuryGate (Infios) entitlements and partner load
Session management
Would need automated session refresh, MFA renewal, and credential rotation with continuous health checks
Data freshness
Real-time for REST flows; near-real-time for EDI 214 status with configurable polling cadence
Security
TLS in transit, encrypted credential vault, scoped per-tenant configurations, audit logging
Webhooks
Outbound webhooks for shipment, status, rate, invoice, and claim events
Latency
Design target: sub-second for cached lookups; seconds for live rate and tender round-trips
Throughput
Design target: horizontally scalable workers tuned to MercuryGate suite limits and EDI partner SLAs
Reliability
Retries with idempotency keys, EDI 997 acknowledgement tracking, and queueing on partner downtime
Versioning
Clear versioning and change management would matter as MercuryGate evolves
Frequently asked questions
Coverage spans Transportation Management & Planning, Rate & Contract Management, Dispatch & Tendering, Visibility & Collaboration, Freight Settlement, and BI - aligned to the suites your tenant has licensed.
Each integration is scoped to your tenant's per-tenant configurations - division/agent codes, custom fields, role-based permissions, rating rules, and EDI partner profiles - so the API matches your operational reality.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual MercuryGate product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.