/dfareporting/v3.5/* → version retirement
Campaign Manager 360 APIStopped working
On February 15, 2023, Campaign Manager 360 API v3.5 shut down. This change affected all calls matching the path /dfareporting/v3.5/*. Requests sent to these endpoints after that date fail and return errors.
Calls it hits
/dfareporting/v3.5/*
What to use instead of these calls
Call a supported version such as /dfareporting/v5/ following the migration guide.
In Campaign Manager 360 API's words
this release marks the beginning of the depreciation period for v3.5, which will sunset on Feb 15, 2023. After this date, any requests made against v3.5 will begin returning errors.
Facts
- API
- Campaign Manager 360 API
dfareporting.googleapis.com - Kind
- Version retirement
- Announced
- June 15, 2022
- Takes effect
- February 15, 2023
- 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/v3.5/* on Campaign Manager 360 API stopped working on February 15, 2023.
What happens to calls after February 15, 2023?
They have failed since February 15, 2023.
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/v4/*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.