2003.JSON Upgrade Compatibility Notes

• To prevent deserialization failures caused by new JSON fields in API responses, developers must proactively adapt their code to handle field additions. As of now, 17VIN guarantees:

No field removal: Legacy fields will always be retained (values may be empty/null). Only additions: New fields will be introduced without breaking existing integrations. Example: VIN Code Decoding ：

**Legacy response：

**New response：