/dfareporting/v4/* → version retirement
Campaign Manager 360 APIStopped working
On February 26, 2026, version v4 of the Campaign Manager 360 API will be retired. This change affects all requests directed to /dfareporting/v4/*. After that date, calls to this version will fail and return errors.
Calls it hits
/dfareporting/v4/*
What to use instead of these calls
Update your integration to call /dfareporting/v5/ instead, following the v4 to v5 migration guide. Moving to the new version requires more than changing the endpoint, as new campaigns need the euPoliticalAdsDeclaration field.
In Campaign Manager 360 API's words
the v5 release marks the beginning of the deprecation period for v4, which will sunset on Feb 26, 2026. After this date, any requests made against v4 will begin returning errors.
Facts
- API
- Campaign Manager 360 API
dfareporting.googleapis.com - Kind
- Version retirement
- Announced
- September 2, 2025
- Takes effect
- February 26, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Campaign Manager 360 API's own pages
Questions
When does this change take effect?
Calls to /dfareporting/v4/* on Campaign Manager 360 API stopped working on February 26, 2026.
What happens to calls after February 26, 2026?
They have failed since February 26, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Campaign Manager 360 API 1
-
/dfareporting/v3.5/*Version retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.