Integrations
The external services TOVR connects to — workspace apps (Gmail, Google Calendar, Google Drive, Outlook) that fOS acts through, and the freight-exchange connectors TOVR ingests loads from and submits bids to. Connections are OAuth-based with encrypted, auto-refreshed credentials.
TOVR connects to external systems on a carrier's behalf. A connection is an org-scoped company integration with its own status and consent; credentials are stored encrypted (referenced, never in the open) and refreshed automatically. This page is the reference for what can be connected; the concepts are in Domain model.
Workspace apps (for fOS)
These let fOS act inside a user's inbox, calendar, and files. Each is connected via OAuth and exposed to fOS as workspace tools.
| App | What fOS can do |
|---|---|
| Gmail | Search threads, read, draft, send, and label mail. |
| Google Calendar | List calendars/events, find availability, create/update/delete events. |
| Google Drive | List, search, read, download, create, and copy files. |
| Microsoft Outlook | Mail and calendar via Microsoft Graph. |
These integrations call the providers' REST APIs through TOVR's own tool layer — they are
not connections to *.mcp.googleapis.com MCP servers. From fOS's perspective the tools look the
same regardless of transport.
Freight-exchange connectors
TOVR ingests loads from — and, where the platform allows, submits bids to — European freight exchanges. Capability varies by platform:
| Exchange | Ingest loads | Submit bids | Notes |
|---|---|---|---|
| Transporeon | ✓ | ✓ | |
| TimoCom | ✓ | ✓ | |
| Trans.eu | ✓ | ✓ | |
| Saloodo | ✓ | ✓ | |
| Lardi-Trans | ✓ | ✓ | |
| Cargopedia | ✓ | publish-only | Publish-only by platform design. |
| Alpega / Teleroute | — | publish-only | Connector in progress; publish-only by platform design. |
Availability of a given exchange depends on the carrier's own access and credentials with that platform. Connecting and managing these lives on the TOVR dashboard's Integrations page — see the Integrations guide.
Telematics & fleet data
TOVR also ingests vehicle positions and driver data from telematics/OEM providers to power matching and hours-of-service checks. These are fleet-data connections rather than developer integrations; see Concepts › Domain model.
Domain model
Field-level reference for TOVR's core entities — shipments, loads, carriers, vehicles, drivers, locations, freight chains, chain legs, matches, and orgs. Representative columns; the source of truth is the Drizzle schema.
What APEX is
APEX is TOVR's freight price intelligence service. It ingests spot-and-executed freight prices from European exchanges, normalizes them into directed corridors, and answers "what does this lane pay?" as p25 / median / p75 percentiles with a confidence score, over a simple API.