Display & Video 360 API
/v2/* version retirement
Stopped workingSubscribe to Display & Video 360 APIShare
On September 3, 2024, Display & Video 360 API version v2 stopped working. Any requests sent to /v2/* endpoints now fail.
Calls it hits
/v2/*
What to use instead of these calls
Call /v4/ instead, following the migration guides on the Display & Video 360 API deprecations page.
In Display & Video 360 API's words
v2 December 6, 2022 February 15, 2024 September 3, 2024 Migrate from v2 to v3
Facts
- API
- Display & Video 360 API
displayvideo.googleapis.com - Kind
- Version retirement
- Announced
- February 15, 2024
- Takes effect
- September 3, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Display & Video 360 API's own pages
Questions
When does this change take effect?
Calls to /v2/* on Display & Video 360 API stopped working on September 3, 2024.
What happens to calls after September 3, 2024?
They have failed since September 3, 2024.
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 Display & Video 360 API 6
-
/v1/*Version retirement Stopped working -
/v3/*Version retirement Stopped working -
/{id}/advertisers/{id}/insertionOrders/{id}/targetingTypes/*Endpoint removal Stopped working -
GET /{id}/advertisers/{id}/campaigns/{id}:listAssignedTargetingOptionsEndpoint removal Stopped working -
GET /{id}/advertisers/{id}/campaigns/{id}/targetingTypes/*Endpoint removal Stopped working -
GET /{id}/advertisers/{id}/insertionOrders/{id}:listAssignedTargetingOptionsEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.