Route proposals
One proposed route for one vehicle within an optimization run.
Fields
The API name is what the API, MCP and the CLI use.
| Name | API name | Type | Required | Description |
|---|---|---|---|---|
| ID | id | Record ID | Yes | |
| Optimization run | logisticsrouteoptimizationrunId | Reference | Yes | |
| Vehicle | vehicleId | Reference | Yes | |
| Total distance | distanceKm | Decimal | Yes | Numeric value stored with decimal precision. |
| Total duration | durationMinutes | Whole Number | Yes | Whole number without fractional part. |
| Created at | createdAt | Date and Time | Yes |
Relations
Owned records (solid line) are deleted with their owner. Grouped records (dashed line) can exist alone.
| Field | Points to | Kind |
|---|---|---|
Optimization run logisticsrouteoptimizationrunId | Optimization runs | owned by |
Vehicle vehicleId | Vehicles | reference |
Actions
What you can do with a record. Every action also sends the webhook event logisticsrouteproposals.<action>. Reads (find, get, count) work on every table.
| Name | API name | Description | Where |
|---|---|---|---|
| Delete | delete | Delete this route proposal and the data that belongs with it. This cannot be undone. | App · WebMCP · API · MCP · CLI |