Display & Video 360 API
GET /{id}/advertisers/{id}/campaigns/{id}/targetingTypes/* endpoint removal
Stopped workingSubscribe to Display & Video 360 APIShare
Calls to GET /{id}/advertisers/{id}/campaigns/{id}/targetingTypes/* on Display & Video 360 API stopped working on February 23, 2026.
Calls it hits
GET /{id}/advertisers/{id}/campaigns/{id}/targetingTypes/*
What to use instead of these calls
Assign targeting directly to line items using advertisers.lineItems.targetingTypes.assignedTargetingOptions when creating them.
In Display & Video 360 API's words
On February 23, 2026, Display & Video 360 will sunset insertion order and campaign targeting.
Facts
- API
- Display & Video 360 API
displayvideo.googleapis.com - Kind
- Endpoint removal
- Takes effect
- February 23, 2026
- 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 GET /{id}/advertisers/{id}/campaigns/{id}/targetingTypes/* on Display & Video 360 API stopped working on February 23, 2026.
What happens to calls after February 23, 2026?
They have failed since February 23, 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 Display & Video 360 API 6
-
/v1/*Version retirement Stopped working -
/v2/*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}/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.