Product update
VehiCode API v1.2.0: possible configurations
VehiCode API v1.2.0 possible configuration updates and integration actions.
What changes
VehiCode API v1.2.0 adds reviewed, model-compatible technical alternatives to the existing possibleConfigurations field for eligible Starter and Business responses where supported data is available.
An alternative is not a factory build identification. A single alternative does not mean the exact vehicle engine has been determined.
How to read the response
In a supported possible configuration, engineCode is "UNKNOWN" when the engine identifier is unavailable. It is not a real engine code and is never published as a verified specification in specs.
The optional coverage: "partial" marker means the alternatives are not an exhaustive list. Existing alternatives with known engine codes remain available in the same field. See the API changelog for the release details.
Integration action
This release is a compatibility-affecting exception within v1. Review strict JSON schemas, engine-code enums, and renderers before handling these responses. The API reference and OpenAPI schema show the new representation.
We are sorry for the complications this may cause. We chose to keep one v1 response and clearly mark partial alternatives because we believe it is the clearest approach for integrations today.
Our new API Versioning & Release Policy explains how we handle Stable API changes and future Beta versions.
v2 Beta remains a future program. Existing billing and subscription entitlements are unchanged.