Locus API
Locus is an end-to-end logistics platform powering order-to-delivery dispatch, route planning, last-mile delivery, hub operations, and carrier management for retail, manufacturing, and 3PL operations. An unofficial API lets you programmatically pull orders, tasks, tours, riders, and tracking data—and push updates like new orders, dispatch plans, and status changes back into Locus.
What is Locus?
Locus is an end-to-end logistics platform that powers order-to-delivery dispatch management for retail, manufacturing, and third-party logistics operations. Acquired by Ingka Group (the world's largest IKEA retailer), Locus serves 360+ brands across 30+ countries with AI-powered route optimization that considers 180+ variables across captive fleets, contracted carriers, and outsourced logistics.
Core product areas include:
- Transportation Management System (TMS) and Dispatch Planning Software
- Last Mile Delivery, Route Planning, and Capacity Management
- Hub Operations (automated sorting, order allocation, returns) and Fulfillment Automation
- Delivery Orchestration, Transporter Management, and ShipFlex flexible carrier fulfillment
- Track and Trace, Control Tower, Driver Companion App, and shipment tracking
- Business Insights dashboards and Location Analytics
Common data entities:
- Orders, Order Items, Customers, Delivery Addresses
- Tasks, Tours, Trips, Dispatch Plans, Routes
- Riders, Vehicles, Fleets, Transporters, Carriers
- Hubs, Capacity Profiles, Service Time Windows
- Tracking Events, Proof of Delivery, Status Updates, Exceptions
The Locus Integration Challenge
Enterprises run mission-critical dispatch and delivery on Locus daily, but turning its platform into clean, API-driven automation is non-trivial:
- Client-gated API access: Locus API integrations are only available to existing Locus clients, with credentials provisioned manually by a Locus representative
- Client ID provisioning: Authentication details and a Client ID are shared by email after a request, rather than self-service onboarding
- Collection-split surface: Order Management, Entity Management, and Platform Entities Management are documented as separate Swagger collections with their own object models
- OpenAPI 2.0 coverage variability: Endpoint availability differs by deployment, product modules enabled, and the client's fulfillment model
- Mobile-sourced operational data: Rider location, proof of delivery, and exceptions flow through the Driver Companion App, not always exposed as clean endpoints
- Multi-party dispatch state: Tasks, tours, and tracking span captive fleets, contracted carriers, and outsourced 3PLs, each with distinct status lifecycles
How Supergood Creates Locus APIs
Supergood reverse-engineers authenticated browser flows and Locus's OpenAPI surface to deliver a resilient API layer for your Locus tenant—across Order Management, dispatch, and tracking.
- Handles Client ID and credentialed authentication securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Orders, Tasks, Tours, Riders, and Tracking so you integrate once and rely on consistent objects
- Aligns with your enabled product modules and fulfillment model to ensure compliant access
Use Locus with AI agents: Locus MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, fulfillment model, and authentication setup.
- Supergood Generates and Validates Your API
We deliver a hardened Locus adapter tailored to your tenant configuration and enabled products.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Locus evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Locus tenant using your Client ID and credentials and obtain a session token for downstream calls.
Order Management
/ordersList orders with filters for status, hub, customer, delivery window, and date range across Order Management.
Order Management
/create_orderCreate a new order with line items, delivery address, and service time window for dispatch planning.
Dispatch
/tasksRetrieve tasks and tours with assignment, rider, and route details across captive and contracted fleets.
Dispatch
/create_dispatch_planSubmit orders for route optimization and generate an assigned dispatch plan across available riders and vehicles.
Tracking
/trackingPull real-time tracking events, proof of delivery, and status updates for tasks and shipments.
Use Cases
Sync orders and delivery status into your stack
- Pull orders, line items, and delivery addresses from Order Management into a central warehouse - Stream task, tour, and tracking events to downstream BI and customer-experience tools - Reconcile order and proof-of-delivery records across hubs for unified order 360
Automate dispatch and route planning
- Push new orders into Locus and trigger route optimization across 180+ variables - Pull generated dispatch plans, tours, and rider assignments back into your OMS or TMS - Route exceptions and reassignments without manual dispatcher clicks
Power live tracking and customer notifications
- Stream real-time rider location and status events into tracking and notification systems - Capture proof of delivery and exceptions from the Driver Companion App - Trigger ETA updates and delivery alerts to customers automatically
Manage carriers and capacity
- Sync transporter, carrier, and ShipFlex fulfillment data into vendor systems - Pull hub capacity profiles and service windows for planning and forecasting - Reconcile delivery performance across captive, contracted, and outsourced fleets
Technical Specifications
Authentication
Client ID and credentialed authentication handled in a managed session
Connectivity
Authenticated browser flows plus Locus's OpenAPI 2.0 surface across Order, Entity, and Platform Entities collections
Response format
Normalized JSON across Orders, Tasks, Tours, Riders, and Tracking objects
Rate limits
Adaptive throttling tuned to your tenant to avoid platform-side limits
Session management
Automatic session refresh, credential rotation, and re-auth handling
Data freshness
Near real-time pulls for orders, tasks, and tracking with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order creation, dispatch assignment, status change, and proof of delivery
Latency
Sub-second reads on cached entities; multi-second writes when posting through dispatch and routing workflows
Throughput
Horizontally scaled workers sized to high-volume order and last-mile delivery operations
Reliability
Retry, backoff, and idempotency keys for order creation and dispatch transactions
Adaptation
Continuous monitoring of Locus releases and tenant-specific configuration drift
Frequently asked questions
Locus API integrations are only available to existing Locus clients, and a Locus representative provisions your Client ID and authentication details. Supergood works on top of your provisioned access to deliver a clean, normalized API layer.
Yes. Supergood normalizes data across Order Management, dispatch tasks and tours, and tracking events into a single API surface, so you integrate once across the full order-to-delivery flow.
Yes. You can push orders into Locus and trigger its route optimization, then pull generated dispatch plans, tours, and rider assignments back into your own OMS or TMS.
Supergood surfaces rider location, proof of delivery, and exception events from Locus's operational layer as normalized tracking objects, even where the mobile app data isn't cleanly exposed as endpoints.
Yes. Tasks, tours, and tracking are normalized across captive fleets, contracted carriers, and outsourced 3PLs, so multi-party dispatch state is consistent regardless of fulfillment model.