Integration Versioning (V2 vs V5)
Background
Support for multiple integration versions was introduced due to backward compatibility issues in Hexon V5.
Hexon V5 introduces major changes in the vehicle object model, primarily:
- pricing structure
- several core vehicle properties
- object field semantics
Additionally, Hexon documentation is inconsistent.
Some changes marked as introduced in version 16 are also present in version 5.
Because vehicles are advertised on third-party platforms that consume specific object fields, changing the object structure causes incompatibility on external websites that are not able to process the new format.
Advertising Logic Change
In V5, the advertising model was redesigned.
Previously:
- A separate site record was created for each vehicle per website.
Now:
- Vehicle state is sent through a dedicated advertising API endpoint.
- Hexon decides internally whether the vehicle should:
- be created on a site
- be updated
- be removed
This removes direct control from the integration layer and delegates publishing logic to Hexon.
Additional Issues
Other incompatibilities and behavioral changes exist and require deeper analysis of the Hexon Swagger specification.
Reference
Hexon Version comparison:
https://api.sandbox.hexon.nl/spi/compare?v5,v2