Optimization runs

A multi-vehicle route optimization request, with its input revision and provider reference.

Fields

The API name is what the API, MCP and the CLI use.

NameAPI nameTypeRequiredDescription
IDidRecord IDYes
Input revisioninputRevisionTextYes
IntegrationlogisticsintegrationIdReference
StatusstatusConstantYesLifecycle or processing state from the allowed values for this record.
Created bycreatedByUser
Created atcreatedAtDate and TimeYes
Updated byupdatedByUser
Updated atupdatedAtDate and TimeYes
Applied byprocessedByUser
Applied atprocessedAtDate and Time
Blocked byblockedByUser
Blocked atblockedAtDate and Time
Archived byarchivedByUser
Archived atarchivedAtDate and Time

Relations

Owned records (solid line) are deleted with their owner. Grouped records (dashed line) can exist alone.

Optimization runsRoute proposals
FieldPoints toKind
Integration logisticsintegrationIdLogistics integrationsreference

Actions

What you can do with a record. Every action also sends the webhook event logisticsrouteoptimizationruns.<action>. Reads (find, get, count) work on every table.

NameAPI nameDescriptionWhere
CreatecreateAdd an new optimization run.App · WebMCP · API · MCP · CLI
EditupdateSave changes to this optimization run.App · WebMCP · API · CLI
ApplyprocessApply the proposed routes to the shipments.App · WebMCP · API · CLI
ArchivearchiveRetire this optimization run from daily use. It leaves active lists and pickers, and most actions stop. Unarchive to restore it.App · WebMCP · API · CLI
RestoreunarchiveReturn this optimization run to active lists and actions.App · WebMCP · API · CLI
DeletedeleteDelete this optimization run and the data that belongs with it. This cannot be undone.App · WebMCP · API · CLI

States

How a record moves from state to state. Archive and block can happen in any state.

ApplyCreatedProcessed