MercuryGate API

Overview

MercuryGate is a shipper-side transportation management system used by enterprise shippers to manage carrier procurement, freight execution, and freight audit across their outbound and inbound freight programs. Its platform covers load tendering and carrier assignment, freight rate management, shipment tracking, and invoice audit, and its adoption among large manufacturers, retailers, and distributors makes it a central data dependency for 3PL platforms, freight audit tools, and carrier management systems that serve enterprise shipper accounts. When a shipper customer runs MercuryGate as their TMS, every adjacent freight tech tool in their logistics operation needs to connect to it to access the load tender and carrier data that drives freight program execution.

TMS API access to MercuryGate is gated entirely behind a formal integration partnership agreement. There is no self-serve developer portal, no sandbox environment outside the partner relationship, and no documented path to production credentials without completing a partnership enrollment with MercuryGate's integration team. The program is structured for established logistics technology vendors with existing commercial relationships with MercuryGate's enterprise shipper customer base, which means the enrollment involves a formal application, technical evaluation, and agreement negotiation. 3PL platforms and freight audit tools that need load tender and carrier portal data to serve their enterprise shipper clients have no self-serve path, and the partnership timeline typically runs multiple quarters from initial application to usable production credentials. For a freight tech team whose enterprise shipper customer needs an integration live to support a specific freight program or audit cycle starting date, the partnership enrollment calendar is a structural barrier.

Integuru generates a production-ready HTTP API for MercuryGate using direct HTTP requests against the same endpoints the MercuryGate web application uses internally for load tender management, carrier assignment, shipment tracking, and invoice processing. The ten planned actions cover the shipper TMS data surfaces that 3PL and freight audit platforms need: load tender listing and creation, carrier management and assignment, real-time shipment tracking, and invoice and settlement retrieval, without a partnership agreement or enrollment process blocking access to the freight program data that enterprise shipper tech is built around.

---

Why Teams Need This Integration

MercuryGate's partner-only access model creates hard dependencies for freight tech teams serving enterprise shipper accounts.

3PL platforms and managed freight services. Third-party logistics platforms that execute freight procurement and carrier management on behalf of enterprise shippers need list_loads, create_load, and assign_carrier to operate as the execution layer for the shipper's MercuryGate freight program. An AI freight procurement agent that can read load tenders from MercuryGate but cannot create new tenders or assign carriers is half-built: it can monitor existing freight activity but cannot run the procurement cycle or tender loads to the shipper's contracted carrier base. list_carriers provides the carrier database with contracted rates and lane coverage that AI procurement tools use to select and assign the optimal carrier for each load based on cost, service, and capacity criteria.

Freight audit and invoice verification platforms. Freight audit tools that verify carrier charges against contracted rates for enterprise shipper clients need list_invoices and get_settlement to pull the full invoice charge breakdown for systematic comparison against rate confirmations and shipper contracts. Enterprise freight audit at scale requires programmatic access to invoice data across hundreds or thousands of shipments per period, and the discrepancy categories that generate the most recovery in freight audit, including accessorial overcharges, incorrect lane rates, and duplicate billings, require line-item invoice data that cannot be extracted efficiently through manual MercuryGate exports. get_load_detail provides the shipment context that freight audit platforms need to validate that carrier charges apply to the correct commodity, weight, and routing.

Carrier portal and shipper visibility tools. Freight tech platforms that build carrier-facing portals for shippers running MercuryGate need list_loads and update_load_status to surface load tender opportunities and receive carrier status updates without requiring carriers to interact directly with the shipper's TMS interface. get_shipment_tracking and update_location feed the shipper visibility portals that 3PL platforms and supply chain visibility tools build on top of MercuryGate freight data, giving shippers real-time status on active loads without requiring them to log into the TMS to pull reports.

Analytics and freight program management tools. Freight analytics platforms that build lane performance, carrier scorecard, and freight spend analysis products for enterprise shippers need programmatic access to MercuryGate load and carrier data to compute the metrics that shipper procurement teams use to manage carrier relationships and negotiate rate renewals. list_loads and get_load_detail feed the data pipelines that analytics tools use to calculate on-time delivery rates, tender acceptance rates, and lane cost trends across the shipper's full freight program.

---

Logistics Workflows This Integration Covers

The ten planned actions cover the shipper TMS and freight program data surfaces that logistics technology teams need from MercuryGate:

• Load tender management: list_loads, get_load_detail, and create_load cover the load tender index, full tender records with carrier and rate data, and new tender creation for 3PL platforms and AI freight procurement agents operating as the shipper's freight execution layer.
• Carrier operations: list_carriers and assign_carrier provide the approved carrier database with contracted rates and lane coverage, and support programmatic carrier assignment and tender transmission for AI procurement and carrier management tools.
• Dispatch status: update_load_status advances load records through carrier acceptance, pickup, transit, and delivery states for freight tech platforms maintaining accurate TMS status without manual shipper entry.
• Shipment tracking and location: get_shipment_tracking and update_location surface real-time shipment position and ETA data for shipper visibility portals and 3PL freight execution platforms monitoring active loads.
• Freight audit and invoicing: get_settlement and list_invoices retrieve freight cost records and carrier invoice line items for freight audit platforms verifying shipper charges against contracted rates.

---

Adjacent Integrations

Integuru already operates in the logistics space in production. The uShip integration delivers live invoice listing for freight and large-item shipping marketplace workflows, demonstrating Integuru's direct HTTP approach on a logistics platform where the standard developer path is unavailable. The MercuryGate integration follows the same architecture: direct HTTP requests against the internal TMS API layer, without browser automation or partnership agreement dependency, delivering sub-3-second response times and 24/7 on-call maintenance on Production plan accounts. uShip is Integuru's only live logistics integration today, making the MercuryGate build an expansion into the shipper-side TMS layer that enterprise freight audit and 3PL platforms depend on.