Reference
The TOVR platform's technical reference — the public REST API (shipments you can write, read-only chains, vehicles, matches, quotes and outreach, the change feed and webhooks, pricing and market analytics), the domain-model field tables, and the external integrations TOVR connects to.
The Reference lane holds the TOVR platform's technical specs. Shared API behavior (bearer format, errors, rate limits, versioning) lives once in API conventions; concepts (what the entities mean) live in TOVR › Concepts.
REST API
A deliberately narrow public API over tovr.eu/api/v1, authenticated with an OAuth 2.0
client-credentials bearer token. The main areas:
- Shipments — create, list, read, and update your shipments.
- Chains, vehicles, matches, quotes and outreach — read-only views of your freight chains, your fleet and published trucks, matches, carrier bids, and the outreach timeline.
- Change feed and Webhooks — follow what changes, by polling or by push.
- Authentication — exchange a client application's credentials for an access token. Client applications themselves are created in the dashboard, under Settings → Developer.
The REST API overview lists every endpoint with the scope it needs, including pricing and market analytics.
The API is intentionally minimal. There are no carrier or shipper directory endpoints, and no writes beyond shipments and webhook endpoints — do not assume them.
Partner integrations
- Factoring partners — how a factoring company
receives
invoice.recordedevents and reads invoice records for the organizations that have consented to it.
Domain model
Field-level reference tables for the entities described in TOVR › Concepts › Domain model.
Integrations
The external services TOVR connects to on a carrier's behalf — integrations (Gmail, Google Calendar, Google Drive, Microsoft Outlook for fOS to act in a user's inbox and calendar), plus the freight-exchange connectors TOVR ingests loads from and submits bids to.
Market & quotes
Two pages that are live but not in the sidebar — the Market directory of carriers and shippers, and Quotes, where you track and answer the bids you have submitted to freight exchanges. Procurement itself happens from the schedule and the freight-chain flows.
REST API overview
The TOVR REST API is a narrow, OAuth2-authenticated surface over tovr.eu/api/v1: ingest and read shipments, read chains, vehicles, matches, quotes and outreach, follow what changes, price lanes, and authenticate.