# API and Data Model Changes Can Break Network Automation

DevFeed: [API and Data Model Changes Can Break Network Automation](<https://devfeed.tech/articles/breaking-apis-or-data-models-is-a-cardinal-sin-11163.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2025/04/api-data-model-contract/>)

Published: 2025-04-29T06:15:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [data](<https://devfeed.tech/topics/data.md>), [networking](<https://devfeed.tech/topics/networking.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [data](<https://devfeed.tech/tags/data.md>), [networking](<https://devfeed.tech/tags/networking.md>), [releases](<https://devfeed.tech/tags/releases.md>)

## AI overview

The article argues that changing APIs or data models between software releases can break tested network automation and force teams to maintain multiple model versions. It contrasts vendors' stability practices and cites examples involving Nokia SR Linux, FRRouting, VyOS, and Cisco IOS.

## Source excerpt

Imagine you decide to believe the marketing story of your preferred networking vendor and start using the REST API to configure their devices. That probably involves some investment in automation or orchestration tools, as nobody in their right mind wants to use curl or Postman to configure network devices. A few months later, after your toolchain has been thoroughly tested, you decide to upgrade the operating system on the network devices, and everything breaks. The root cause: the vendor changed their API or the data model between software releases. Read more ...