Product update
Stable normalized body styles in the VehiCode API
VehiCode now returns bodyStyleNormalized, a stable canonical body style field for VIN decoder API integrations.
Two fields for two jobs
Vehicle body labels often vary by market, source, and manufacturer wording. A wagon can appear as Combi, Estate, Touring, or Station Wagon depending on the data source.
VehiCode now keeps the detailed label in bodyStyle and adds bodyStyleNormalized as a stable value for application logic.
What integrators should use
Use bodyStyle when you want a readable vehicle label for operators or customer-facing detail.
Use bodyStyleNormalized when you need a predictable machine-readable category for filters, enums, imports, and downstream integrations.
Decode response excerpt
{
"bodyStyle": "Combi",
"bodyStyleNormalized": "wagon"
}
{
"bodyStyle": "Convertible",
"bodyStyleNormalized": "cabrio"
}Backward compatible by design
This is an additive API change. Existing bodyStyle values are not renamed or removed.
Integrators no longer need to map common source labels such as Combi, Estate, Touring, or Station Wagon before storing a stable category.
FAQ
Does this change existing bodyStyle values?
No. bodyStyle remains the detailed source label. bodyStyleNormalized is added alongside it.
Which field should integrations store?
Store bodyStyleNormalized for enum-like logic and keep bodyStyle when you need the detailed human-readable label.