@solvice/routing 0.17.8-beta.0 → 0.18.0-beta.0

package/dist/runs.d.ts

@@ -697,10 +697,11 @@ export interface components {
             time_windows?: components["schemas"]["TimeWindow"][] | null;
         };
         /**
-         * @description Which road-network data prices travel times and distances.
+         * @description Which data prices travel times and distances. Omitted, it follows
+         *     `travel.departure_time`: `osm` without one, `tomtom` with one.
          *
-         *     - `tomtom` (default): TomTom historical-typical traffic at the departure
-         *       time.
+         *     - `tomtom`: TomTom historical-typical traffic at the departure time, or at
+         *       the moment of the request without one.
          *     - `osm`: OpenStreetMap free-flow times. No traffic, so
          *       `travel.departure_time` is rejected with 400.
          *     - `tomtom_real_time`: TomTom live traffic at the moment of the request.
@@ -708,10 +709,13 @@ export interface components {
          *       `travel.departure_time` is rejected; every vehicle must use the `car`
          *       profile; at most 100 distinct locations; up to ~25 s of matrix fetch at
          *       100 locations.
+         *     - `straight_line`: great-circle distance at `travel.speed_kmh`, no road
+         *       network. `travel.departure_time`, `options.polyline` and any vehicle
+         *       `profile` other than `car` are rejected with 400.
          * @example osm
          * @enum {string}
          */
-        MatrixEngine: "tomtom" | "osm" | "tomtom_real_time";
+        MatrixEngine: "tomtom" | "osm" | "tomtom_real_time" | "straight_line";
         /**
          * @description Top-level objective configuration.
          *
@@ -1158,7 +1162,7 @@ export interface components {
          *       "type": "sequence"
          *     }
          */
-        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
+        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationConsecutive"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
         /**
          * All or none
          * @description All or none: either every member in `stops` is served, or none is.
@@ -1216,6 +1220,29 @@ export interface components {
              */
             type: "compatible_vehicles";
         };
+        /**
+         * Consecutive
+         * @description Ordering with no gap: like `sequence`, and in addition no other stop may
+         *     sit between two neighbouring members that are served on the same
+         *     route. A member that is unassigned is skipped, so only listed
+         *     neighbours that are both served are adjacent. Members on different
+         *     routes are unconstrained; add `same_route` to keep them together.
+         */
+        RelationConsecutive: {
+            /**
+             * @description Job ids or shipment-leg stop ids, in the order they must be served
+             *     back to back. At least 2. A stop has one successor and one predecessor
+             *     across all `consecutive` relations, so `[a, b]` and `[b, c]` may
+             *     overlap but `[a, b]` and `[a, c]` may not. A shipment's own id is rejected with HTTP
+             *     400 `not_supported`.
+             */
+            stops: string[];
+            /**
+             * @description Discriminator: always `consecutive`. (enum property replaced by openapi-typescript)
+             * @enum {string}
+             */
+            type: "consecutive";
+        };
         /**
          * @description Which instant of a member a `synchronized` or `time_lag` relation is
          *     measured at, named after the response stop field that reports it. There is
@@ -1974,6 +2001,7 @@ export interface components {
              *     `estimate` (the default) solves on estimated travel and sets
              *     `summary.travel_estimated`; `fail` returns the 502/503 instead.
              *     Locations that Maps rejects for spanning more than one region are a 400.
+             *     No effect with `travel.engine: "straight_line"`, which fetches nothing.
              * @default estimate
              */
             travel_fallback?: null | components["schemas"]["TravelFallback"];
@@ -3196,7 +3224,8 @@ export interface components {
              *     `score.violation_count` hold only against it, and no `routes[].polyline`
              *     is returned. Solve again once Maps is back if the plan must hold on the
              *     road; on a solve, `options.travel_fallback: "fail"` returns the error
-             *     instead. Absent when travel is road-routed.
+             *     instead. Absent when travel came from the requested engine,
+             *     `straight_line` included.
              */
             travel_estimated?: boolean;
             /**
@@ -3222,7 +3251,8 @@ export interface components {
             /**
              * Format: double
              * @description Cost, in the objective's currency, incurred when a task without this
-             *     tag is served. Must be finite and `>= 0`.
+             *     tag is served. Must be finite and `>= 0`, and one vehicle's entries
+             *     must sum to at most 21474.83647 (a task lacking every tag pays them all).
              * @example 25
              */
             violation_cost: number;
@@ -3464,11 +3494,13 @@ export interface components {
         /**
          * @description Where travel times and distances come from.
          *
-         *     Matrices are traffic-aware (historical-typical traffic); by default travel
-         *     times reflect traffic at the moment the request is processed. Set
-         *     `departure_time` to plan against another instant — e.g. tomorrow's 08:00
-         *     routes with morning-rush travel times, or a replay of a past run under its
-         *     original conditions.
+         *     Omitted altogether, travel times are free-flow (`osm`): the same request
+         *     prices the same at any hour. Set `departure_time` to plan against an
+         *     instant's traffic — e.g. tomorrow's 08:00 routes with morning-rush travel
+         *     times, or a replay of a past run under its original conditions; the engine
+         *     is then `tomtom`. Set `engine: tomtom` alone for traffic at the moment the
+         *     request is processed. `engine: "straight_line"` skips the road network for
+         *     great-circle travel at `speed_kmh`.
          * @example {
          *       "departure_time": "2026-07-01T08:00:00+02:00",
          *       "engine": "tomtom"
@@ -3478,16 +3510,27 @@ export interface components {
             /**
              * Format: date-time
              * @description Departure time for the traffic lookup (RFC 3339 instant, any offset).
-             *     Omitted → traffic at solve time. An explicit departure time bypasses
-             *     the server-side matrix cache.
+             *     Omitted → free-flow times, or traffic at solve time with `engine:
+             *     tomtom`. An explicit departure time bypasses the server-side matrix
+             *     cache.
              * @example 2026-07-01T08:00:00+02:00
              */
             departure_time?: string | null;
             /**
-             * @description Road-network data behind travel times and distances. Omitted →
-             *     `tomtom`.
+             * @description Data behind travel times and distances. Omitted → `osm`, or `tomtom`
+             *     when `departure_time` is set.
              */
             engine?: null | components["schemas"]["MatrixEngine"];
+            /**
+             * Format: double
+             * @description Travel speed for `engine: "straight_line"`, in km/h: each leg takes its
+             *     great-circle distance at this speed, rounded to the whole second. `1` to
+             *     `1000`, default `50`; `vehicles[].speed_factor` still scales it per
+             *     vehicle. Any other engine rejects it (HTTP 400 `conflicting_fields`).
+             * @default 50
+             * @example 50
+             */
+            speed_kmh?: number | null;
         };
         /**
          * @description `options.travel_fallback`: what a solve does when travel times cannot be

package/dist/v3.d.ts

@@ -883,10 +883,11 @@ export interface components {
             time_windows?: components["schemas"]["TimeWindow"][] | null;
         };
         /**
-         * @description Which road-network data prices travel times and distances.
+         * @description Which data prices travel times and distances. Omitted, it follows
+         *     `travel.departure_time`: `osm` without one, `tomtom` with one.
          *
-         *     - `tomtom` (default): TomTom historical-typical traffic at the departure
-         *       time.
+         *     - `tomtom`: TomTom historical-typical traffic at the departure time, or at
+         *       the moment of the request without one.
          *     - `osm`: OpenStreetMap free-flow times. No traffic, so
          *       `travel.departure_time` is rejected with 400.
          *     - `tomtom_real_time`: TomTom live traffic at the moment of the request.
@@ -894,10 +895,13 @@ export interface components {
          *       `travel.departure_time` is rejected; every vehicle must use the `car`
          *       profile; at most 100 distinct locations; up to ~25 s of matrix fetch at
          *       100 locations.
+         *     - `straight_line`: great-circle distance at `travel.speed_kmh`, no road
+         *       network. `travel.departure_time`, `options.polyline` and any vehicle
+         *       `profile` other than `car` are rejected with 400.
          * @example osm
          * @enum {string}
          */
-        MatrixEngine: "tomtom" | "osm" | "tomtom_real_time";
+        MatrixEngine: "tomtom" | "osm" | "tomtom_real_time" | "straight_line";
         /**
          * @description Top-level objective configuration.
          *
@@ -1391,7 +1395,7 @@ export interface components {
          *       "type": "sequence"
          *     }
          */
-        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
+        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationConsecutive"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
         /**
          * All or none
          * @description All or none: either every member in `stops` is served, or none is.
@@ -1449,6 +1453,29 @@ export interface components {
              */
             type: "compatible_vehicles";
         };
+        /**
+         * Consecutive
+         * @description Ordering with no gap: like `sequence`, and in addition no other stop may
+         *     sit between two neighbouring members that are served on the same
+         *     route. A member that is unassigned is skipped, so only listed
+         *     neighbours that are both served are adjacent. Members on different
+         *     routes are unconstrained; add `same_route` to keep them together.
+         */
+        RelationConsecutive: {
+            /**
+             * @description Job ids or shipment-leg stop ids, in the order they must be served
+             *     back to back. At least 2. A stop has one successor and one predecessor
+             *     across all `consecutive` relations, so `[a, b]` and `[b, c]` may
+             *     overlap but `[a, b]` and `[a, c]` may not. A shipment's own id is rejected with HTTP
+             *     400 `not_supported`.
+             */
+            stops: string[];
+            /**
+             * @description Discriminator: always `consecutive`. (enum property replaced by openapi-typescript)
+             * @enum {string}
+             */
+            type: "consecutive";
+        };
         /**
          * @description Which instant of a member a `synchronized` or `time_lag` relation is
          *     measured at, named after the response stop field that reports it. There is
@@ -2855,6 +2882,7 @@ export interface components {
              *     `estimate` (the default) solves on estimated travel and sets
              *     `summary.travel_estimated`; `fail` returns the 502/503 instead.
              *     Locations that Maps rejects for spanning more than one region are a 400.
+             *     No effect with `travel.engine: "straight_line"`, which fetches nothing.
              * @default estimate
              */
             travel_fallback?: null | components["schemas"]["TravelFallback"];
@@ -3500,7 +3528,8 @@ export interface components {
              *     `score.violation_count` hold only against it, and no `routes[].polyline`
              *     is returned. Solve again once Maps is back if the plan must hold on the
              *     road; on a solve, `options.travel_fallback: "fail"` returns the error
-             *     instead. Absent when travel is road-routed.
+             *     instead. Absent when travel came from the requested engine,
+             *     `straight_line` included.
              */
             travel_estimated?: boolean;
             /**
@@ -3526,7 +3555,8 @@ export interface components {
             /**
              * Format: double
              * @description Cost, in the objective's currency, incurred when a task without this
-             *     tag is served. Must be finite and `>= 0`.
+             *     tag is served. Must be finite and `>= 0`, and one vehicle's entries
+             *     must sum to at most 21474.83647 (a task lacking every tag pays them all).
              * @example 25
              */
             violation_cost: number;
@@ -3827,11 +3857,13 @@ export interface components {
         /**
          * @description Where travel times and distances come from.
          *
-         *     Matrices are traffic-aware (historical-typical traffic); by default travel
-         *     times reflect traffic at the moment the request is processed. Set
-         *     `departure_time` to plan against another instant — e.g. tomorrow's 08:00
-         *     routes with morning-rush travel times, or a replay of a past run under its
-         *     original conditions.
+         *     Omitted altogether, travel times are free-flow (`osm`): the same request
+         *     prices the same at any hour. Set `departure_time` to plan against an
+         *     instant's traffic — e.g. tomorrow's 08:00 routes with morning-rush travel
+         *     times, or a replay of a past run under its original conditions; the engine
+         *     is then `tomtom`. Set `engine: tomtom` alone for traffic at the moment the
+         *     request is processed. `engine: "straight_line"` skips the road network for
+         *     great-circle travel at `speed_kmh`.
          * @example {
          *       "departure_time": "2026-07-01T08:00:00+02:00",
          *       "engine": "tomtom"
@@ -3841,16 +3873,27 @@ export interface components {
             /**
              * Format: date-time
              * @description Departure time for the traffic lookup (RFC 3339 instant, any offset).
-             *     Omitted → traffic at solve time. An explicit departure time bypasses
-             *     the server-side matrix cache.
+             *     Omitted → free-flow times, or traffic at solve time with `engine:
+             *     tomtom`. An explicit departure time bypasses the server-side matrix
+             *     cache.
              * @example 2026-07-01T08:00:00+02:00
              */
             departure_time?: string | null;
             /**
-             * @description Road-network data behind travel times and distances. Omitted →
-             *     `tomtom`.
+             * @description Data behind travel times and distances. Omitted → `osm`, or `tomtom`
+             *     when `departure_time` is set.
              */
             engine?: null | components["schemas"]["MatrixEngine"];
+            /**
+             * Format: double
+             * @description Travel speed for `engine: "straight_line"`, in km/h: each leg takes its
+             *     great-circle distance at this speed, rounded to the whole second. `1` to
+             *     `1000`, default `50`; `vehicles[].speed_factor` still scales it per
+             *     vehicle. Any other engine rejects it (HTTP 400 `conflicting_fields`).
+             * @default 50
+             * @example 50
+             */
+            speed_kmh?: number | null;
         };
         /**
          * @description `options.travel_fallback`: what a solve does when travel times cannot be

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solvice/routing",
-  "version": "0.17.8-beta.0",
+  "version": "0.18.0-beta.0",
   "description": "TypeScript client for the Solvice V3 routing API, generated from its OpenAPI spec.",
   "license": "Apache-2.0",
   "homepage": "https://docs.solvice.io/guides/platform/sdks/typescript",