Integrations
Dock Optimizer connects to the stack you already run
Eight prebuilt connectors and a Generic REST fallback mean you rarely need custom code. Prebuilt connectors are live in under 30 minutes. Custom REST integrations typically take an afternoon.
Available connectors
All connectors ship with retry logic, dead-letter queuing, and tenant isolation.
Poll SphereWMS's REST API v2 to bring inventory levels and order/receipt feeds into your dock schedule — no manual re-entry.
- SphereWMS
- Generic WMS via REST
Pull live ETA predictions into Dock Optimizer so your team knows a truck is running late before it calls.
- FourKites
- project44
Inbound 204 load tenders create Load records automatically. Outbound 214, 210, and 990 transmit on milestones. Per-partner config, swappable transport.
- X12 204 (load tender)
- X12 214, 210, 990
Connect dock levelers, door monitors, and yard cameras to close the loop between the digital schedule and the physical dock.
- MQTT door sensors
- Generic sensor bridge
Pull dock utilization, dwell time, and detention data into the BI tools leadership already uses — via a scoped API key, no middleware.
- Power BI
- Tableau
- Any REST-capable BI tool
Configure field mappings, authentication, and retry logic for any API endpoint your stack exposes.
- Generic REST connector
- Outbound webhooks
Featured integration
Warehouse Management
SphereWMS + Dock Optimizer
The SphereWMS connector is live and production-tested with a real 3PL. Dock Optimizer polls SphereWMS's REST API v2 on a configurable interval to pull inventory levels and order/receipt feeds into the dock schedule — eliminating the clipboard handoff between the dock office and the warehouse floor.
Need the full technical picture?
The Integration Hub page covers connector configuration, OAuth2 token handling, retry behavior, the MCP surface, and the REST API reference.
Go to Integration Hub