This was a bad decision. Api change should never be made in 48 hours for a single customer. These are the kinds of decisions you are stuck with for years. Worse, if you ever want to get rid of it, you can't! Good Apis don't slide the carpet out under dev's feet.
Making knee-jerk, one-off decisions are a sure sign of bad things to come.
You want to have a system in place that is adaptable and flexible for its end users, but strict enough so that it doesn"t break production or core systems. This is where agile development and quality assurance comes in.
I think in this case the requests made were already on the development roadmap, and were escalated with the request. It is not unrealistic for any high performance team to crank out these types of requests in 2 full days, and still maintain a solid API platform.
Plan, Do, Check, Act is aleays the best method for long term product quality assurance. Eventually all systems will have a need for some type of update that makes improvements or innovatations to its code base. Its how you deploy those changes which determines the updates success.
Making knee-jerk, one-off decisions are a sure sign of bad things to come.