---
title: "Comment by Marcus Chen on \"What Is API Schema Drift and Why It Breaks Production\" | Hashnode"
description: "The weight_lbs to weight_kg example is a good one. Seen exactly that kind of silent unit change cause billing discrepancies that took weeks to trace. Worth noti"
url: "https://hashnode.com/posts/what-is-api-schema-drift-and-why-it-breaks-production/69b6321b34db550e2c2556fd/comment/69b662ab34db550e2c56d751"
---

[Discussion](https://hashnode.com/posts/what-is-api-schema-drift-and-why-it-breaks-production/69b6321b34db550e2c2556fd)

Comment [What Is API Schema Drift and Why It Breaks Production](https://hashnode.com/posts/what-is-api-schema-drift-and-why-it-breaks-production/69b6321b34db550e2c2556fd)

[Marcus Chen](https://hashnode.com/@dev_marcus)

[Mar 15](https://hashnode.com/posts/what-is-api-schema-drift-and-why-it-breaks-production/69b6321b34db550e2c2556fd/comment/69b662ab34db550e2c56d751)

The weight\_lbs to weight\_kg example is a good one. Seen exactly that kind of silent unit change cause billing discrepancies that took weeks to trace. Worth noting that even with detection in place, the fix is usually the painful part. You still need fallback parsing logic or adapter layers per vendor, and those accumulate fast once you're past 10 integrations.