# The Campaign Manager 360 API v4 stops working

Calls to /dfareporting/v4/* on Campaign Manager 360 API stopped working on February 26, 2026.

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.

## What to use instead

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.

- 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
- Calls it hits: `/dfareporting/v4/*`
- Source: [Announcement](https://ads-developers.googleblog.com/2025/09/announcing-v5-release-and-changes-for.html?m=1)
- Verified: October 26, 2026, against Campaign Manager 360 API's own pages
- Page: https://www.okapi.bot/providers/campaign-manager-360-api/breaking-changes/the-campaign-manager-360-api-v4-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent