McLeod Software API

Overview

McLeod Software is the dominant transportation management system for asset and non-asset trucking carriers in North America, with deep adoption among large truckload, LTL, and owner-operator networks that treat it as the operational core of their freight business. Load management, driver pay, carrier settlement, and dispatch operations all run through McLeod at enterprises that have standardized on it, making it a non-negotiable integration dependency for freight tech platforms building carrier portals, AI dispatch tools, accounting automation systems, and analytics products that serve the trucking market. When a carrier customer runs McLeod, every adjacent tool in their stack needs to connect to it to be useful.

API access to McLeod is gated entirely behind a formal partner program. There is no self-serve developer portal, no sandbox environment available outside the partner relationship, and no documented path to production credentials without completing a partnership agreement. The program is structured for established ISVs with existing McLeod customer relationships, which means the enrollment involves a formal application, business case review, technical certification, and agreement negotiation. Freight tech teams and AI dispatch platform vendors that need load, driver, and settlement data to serve their carrier customers cannot access the McLeod TMS layer without completing this process, and the timeline typically runs multiple quarters from initial application to usable production credentials. For an engineering team building a carrier portal integration against an enterprise go-live date, this is a structural problem without a workaround inside the partner program.

Integuru generates a production-ready HTTP API for McLeod Software using direct HTTP requests against the same endpoints the McLeod web application uses internally for load management, driver operations, and carrier settlement. The ten planned actions cover the TMS data surfaces that freight tech and AI dispatch teams need: load listing and tendering, carrier assignment and reassignment, real-time shipment tracking, driver position updates, and settlement and invoice retrieval, without a partner program enrollment or certification blocking access to the operational data that carrier-side freight tech is built around.

---

Why Teams Need This Integration

McLeod Software's partner-only access model creates hard dependencies for freight tech teams across several categories of carrier-side product.

Carrier portals and driver-facing applications. Freight tech platforms building white-label carrier portals or driver-facing mobile applications for McLeod carriers need list_loads, get_load_detail, and get_settlement as live API calls against the TMS. A carrier portal that cannot query current load assignments and driver pay data from McLeod in real time cannot serve as the driver's primary operational interface, because the data it displays goes stale the moment a dispatcher makes a change in the TMS. list_invoices gives the carrier's accounts receivable team current billing status without requiring them to log into McLeod to pull reports, and get_shipment_tracking surfaces the shipment position data that shipper-facing tracking portals need to show customers real-time load progress.

AI dispatch agents and freight automation platforms. An AI dispatch agent that can read loads from McLeod but cannot update carrier assignments or shipment status is half-built. create_load, assign_carrier, and update_load_status are the write actions that close the dispatch loop, letting an AI agent tender loads against carrier capacity and rate criteria, assign the optimal carrier, and advance the load through dispatch states as the shipment progresses, all without requiring a human dispatcher to touch every load in the TMS. For freight tech teams building AI-native dispatch tools for asset carriers running McLeod, these write actions are the difference between an advisory tool and one that actually reduces dispatcher workload.

Accounting automation and settlement reconciliation tools. Freight accounting platforms and driver pay automation systems that serve McLeod carriers need get_settlement and list_invoices to pull pay and billing records for reconciliation, payroll processing, and accounts receivable aging without relying on McLeod's scheduled report exports. list_carriers gives compliance and insurance verification tools a current carrier roster with authority and insurance status, which is a prerequisite for automated carrier onboarding workflows and compliance monitoring platforms that serve brokers and carriers simultaneously.

Analytics and business intelligence platforms. Freight analytics platforms that surface load performance, carrier utilization, and lane profitability data for McLeod carriers need programmatic access to load records and carrier data to build metrics that the TMS does not surface natively. list_loads and get_load_detail feed the data pipelines that analytics platforms use to calculate lane performance, carrier acceptance rates, and on-time delivery metrics across the carrier's full freight operation.

---

Logistics Workflows This Integration Covers

The ten planned actions cover the core TMS data and dispatch surfaces that freight tech teams need from McLeod Software:

• Load management: list_loads, get_load_detail, and create_load cover the load index, full load records with carrier and rate data, and load tendering for AI dispatch agents and carrier portal applications connecting to McLeod.
• Carrier operations: list_carriers and assign_carrier give freight tech platforms current carrier roster data and the ability to assign or reassign carriers to loads programmatically, enabling AI dispatch and compliance tools to operate on live carrier records.
• Shipment tracking and location: get_shipment_tracking and update_location surface real-time shipment position and ETA data and support driver position pushes for tracking portals and AI dispatch agents monitoring active loads.
• Dispatch status: update_load_status advances load records through pickup, in-transit, delivered, and exception states, enabling AI dispatch agents to maintain an accurate TMS picture as shipments progress without manual dispatcher intervention.
• Settlements and invoicing: get_settlement and list_invoices surface driver pay records and carrier invoicing data for accounting automation, driver pay platforms, and accounts receivable tools serving McLeod carriers.

---

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 no official developer API exists. The McLeod Software integration follows the same architecture: direct HTTP requests against the internal TMS API layer, without browser automation or partner program 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 McLeod build an expansion of proven freight tech infrastructure into the carrier TMS layer.