PCS McLeod API
McLeod Software (LoadMaster for asset-based carriers and PowerBroker for freight brokers) is transportation management software used by trucking fleets and brokerages to run orders, dispatch drivers/equipment, exchange EDI, track loads, and bill customers. An unofficial API lets you p
What is McLeod?
McLeod Software provides transportation management systems (TMS) for carriers and brokers. LoadMaster centralizes fleet operations (orders, dispatch, drivers, tractors/trailers, EDI, settlements), while PowerBroker manages brokerage workflows (customer/capacity management, rating, tendering, carrier pay). Organizations use McLeod to plan and execute loads, manage stops and appointments, communicate with drivers, track progress via mobile/ELD integrations, and handle billing and settlements.
Core product areas include:
- Order & Load Management (e.g., customers, reference numbers, PRO/BOL, stops and appointments)
- Dispatch & Driver/Equipment (e.g., driver assignments, tractors/trailers, planned/actual times)
- Tracking & Visibility (e.g., status events, geolocation, ETA, documents like POD)
- Financials (e.g., rating, accessorials, invoices/AR, settlements/AP)
- EDI & Integrations (e.g., 204 tender, 990 response, 214 status, 210 invoice)
Common data entities:
- Companies (customers/bill-to, carriers, divisions), Users, and Permissions
- Loads (metadata, references, division codes, statuses)
- Stops & Appointments (pickup/delivery, windows, locations)
- Drivers, Tractors, Trailers (assignments, unit numbers)
- Tracking Events (arrived, departed, delivered, POD)
- Rates & Accessorials (line items, fuel surcharge)
- Invoices/Settlements (AR/AP, terms, attachments)
The McLeod Integration Challenge
Fleets and brokerages rely on McLeod daily, but turning portal-based and EDI-driven workflows into API automation is non-trivial:
- Deployment model variability: Many tenants are on-prem or private cloud with custom modules and entitlements; connectivity and authentication differ by customer
- Module/licensing gates: Access to loads, dispatch, EDI, documents, and financials often depends on purchased modules, making uniform API coverage tricky
- Portal-first features: Document imaging (e.g., BOL/POD), appointment editing, and driver messaging are optimized for the thick client/web app with data spread across distinct views
- Status rigor: Load lifecycle transitions and financial postings have strict business rules; incorrect updates can break downstream settlement
- EDI-centric ecosystems: Tenders, status, and invoices may be batched via EDI jobs; polling and event capture require careful orchestration to achieve real-time behavior
- Permissions: Role-based controls and division/company codes impact visibility and write access, complicating headless automation
How Supergood Creates McLeod APIs
Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your McLeod tenant.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses so you can integrate once and rely on consistent objects across modules
- Aligns with customer entitlements, division codes, and role-based permissions to ensure compliant access
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules (LoadMaster/PowerBroker), licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened McLeod adapter tailored to your workflows, divisions, and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as McLeod evolves.
API Endpoints
Authentication
/sessionsEstablish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.
Authentication
/sessions/refreshRefresh an existing token to keep sessions uninterrupted.
Loads
/loadsList loads with filters and summary details.
Loads
/loadsCreate a new load with stops, equipment, and rate details.
Dispatch
/loads/{loadId}/dispatchesAssign a driver, tractor, and trailer, and set planned times.
Tracking & Status Events
/loads/{loadId}/status-eventsAppend a status update (arrived, departed, delivered, POD) with optional geolocation and attachments.
Tracking & Status Events
/loads/{loadId}/status-events(POD example): Submit delivery with proof-of-delivery attachment.
Invoices (Accounts Receivable)
/loads/{loadId}/invoicesCreate an invoice against a delivered load with line items and attachments.
Use Cases
Load & Company Data Sync
- Mirror loads, customers, carriers, and divisions into your internal systems - Keep stop metadata and appointment windows current for visibility and planning - Normalize references (PRO/BOL/customer order) for analytics and customer portals
Dispatch Automation
- Assign drivers, tractors, and trailers from your planning engine - Push plan times and messages to drivers; update appointments dynamically - Keep unit assignments and driver status aligned across safety/compliance systems
Tracking & POD
- Ingest arrived/departed/delivered events from ELD/telematics and mobile apps - Attach POD images and documents; trigger customer notifications - Drive ETA alerts and exception workflows when thresholds are breached
Financials: Rating, Invoices, and Settlements
- Create invoices from completed loads with line items and surcharges - Pull invoice status to reconcile AR/AP with ERP (e.g., NetSuite, QuickBooks) - Capture accessorials programmatically and ensure auditability
Technical Specifications
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination across modules
Rate limits
Tuned for enterprise throughput while honoring customer entitlements, division codes, and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of loads, dispatch, tracking, and financial objects—even in EDI-heavy environments
Security
Encrypted transport, scoped tokens, and audit logging; respects McLeod role-based permissions and business rules
Webhooks
Optional asynchronous delivery for long-running workflows (e.g., invoice approvals, settlement posting)
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume load sync, dispatch assignment, and status event ingestion
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions and protect financial postings
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Frequently asked questions
Supergood supports workflows across commonly used areas such as Order/Load Management, Dispatch (drivers, tractors/trailers), Tracking (status events, geolocation), Financials (rating, invoices/AR, settlements), and document handling (BOL/POD), subject to your licensing and entitlements. We scope coverage during integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For on-prem/private cloud, we establish secure connectivity and session maintenance based on your environment. Sessions are refreshed automatically with secure challenge handling.
Yes. We can normalize loads, stop details, and invoices to match your ERP/analytics schema (e.g., cost centers, charge codes) and deliver updates via webhooks or polling while complying with rate and permission constraints.
We enforce McLeod business rules for status transitions and protect financial operations with idempotency and validations (e.g., delivered before invoicing). We align with your approval chains and division codes to ensure compliant updates.