42
What's the best way to monitor an API for breaking changes?
(sh.itjust.works)
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
I'm 3,500 miles from the vendor's devs, sadly.
Asking them to put the swagger file itself behind the API is a good idea. Their dev backlog is 3-24 months.
I used the same trick to determine the required headers and parameters - I checked their website which uses the same API.
The source of their delays is that different devs or teams "own" different endpoints and make their changes without documenting. It's annoying, stuff like the same data being in field "hostId" on one endpoint but "deviceId" on another.
Just build a few selenium Tests to ensure the API requests the website performs don't change without you noticing :)
That's not a bad idea. Usually, so far, their frontend team doesn't hear about the changes either!
Wow that's bad practice. Sell your monitoring to them to help improve their quality.
I honestly think we provide a significant impetus for improvement on their side. They have lots of other customers, but most aren't as involved and embedded in the data as we are.
This is why you have requirements which are agreed upon and affect payment if not upheld. If you start being firmer, they might move quicker. 24 month lead team is bullshit.
They have accepted the penalties as the cost of doing business, and the decision makers on my side are worried about opening it up again. It's a custom hardware + custom software thing so there aren't that many options!