When we released V21 of the Google Ads API, we released a field with the wrong name in the BudgetPerDayMinimumErrorDetails minimum_budget_amount_micros was mistakenly released as minimum_bugdet_amount_micros, with the word “budget” misspelled.
We already corrected the error in V22 of the API; however, we are also retroactively correcting it in V21 starting from October 15th, 2025 (the same day of the V22 release).
What do I need to do?
If you are using one of our officially supported client libraries , they will keep working seamlessly when we release the field rename.
However, when you upgrade to the latest version of your client library, you will have to modify your existing code that accesses this field to comply with the field rename, even if you are still using V21.
If you are using the Google Ads API with the REST transport layer, make sure your code is handling the minimum_budget_amount_micros field by its correct name instead of the mistakenly released one.
If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server .
