PTV Logistics Product Forum

Route Optimization API OpenAPI Update Analysis (v1.38 → v1.39)

This post summarizes the structural changes between the OpenAPI specifications
v1.38 and v1.39.

The focus is on schema / model changes that are relevant for client integrations.

1) Endpoints / Paths

No changes

There are no new, removed, or modified endpoints between v1.38 and v1.39.

All existing routes remain unchanged, including:

• /optimizations
• /optimizations/{id}
• /optimizations/{id}/progress
• /optimizations/{id}/metadata
• /optimizations/{id}/request
• /optimizations/{id}/stop

This release does not affect routing, URLs, or HTTP semantics.

2) Component Schemas
No new schemas introduced

• All component schemas present in v1.39 already existed in v1.38.

No new object types were added at schema level.

3) Existing Schemas – Structural Changes
Result: No structural schema changes detected

A detailed comparison of the component schemas shows:

• No new properties added to existing schemas
• No properties removed
• No changes to required/optional semantics
• No type changes

The schema structure is identical between v1.38 and v1.39.

4) Cost-related Models

All cost-related schemas (including route-level and result-level costs):

• remain unchanged
• have the same structure and semantics as in v1.38

There are no changes in cost modeling between these versions.

5) Required / Optional Semantics

There are:

• no new required fields
• no changes to existing required definitions
• no changes regarding nullable vs. non-nullable fields

From a validation and deserialization perspective, v1.39 behaves exactly like v1.38.

6) Client Impact / Compatibility Notes

Fully backward compatible

• No DTO changes required
• No regeneration strictly necessary for structural reasons
• Existing clients built against v1.38 will continue to work unchanged

v1.39 is a non-breaking, no-impact update for client integrations.

7) Summary

PTV OptiFlow OpenAPI v1.39 introduces no structural changes compared to v1.38.

• No endpoint changes
• No schema changes
• No cost model changes
• No required/optional changes
• Fully backward compatible

From an API consumer perspective, v1.39 is effectively equivalent to v1.38.

Final note

• This comparison is strictly based on OpenAPI structure.
  Behavioral changes (e.g. different result values or optimization logic) cannot be inferred from the specification alone.