API Platform Changes & Migration Guide (2026)

Document Version: 3.0.0 Last Updated: February 12, 2026 Status: 🔴 CRITICAL UPDATES — MULTIPLE DEADLINES ACTIVE

Executive Summary

This document tracks critical API platform changes from Meta, Google, Salesforce, and Amazon that affect MIZ OKI's reporting, integrations, and messaging flows. All changes have been reviewed against our current implementation and integration status has been verified.

New in v2.0.0: Comprehensive API versioning, authentication patterns, rate limits, and Boss Agent skill signatures for all major platforms.

📊 API Versions, Auth Patterns & Quotas (Quick Reference)

🔴 Critical Deadlines

📌 Detailed API Platform Specifications

🔴 Google Ads API

February 2026 Breaking Changes:

1. v19 Sunset (Feb 11, 2026): All v19 requests now return errors. Systems MUST use v20, v21, or v22.
2. Session/IP Fields (Feb 2, 2026): New session-attribute or IP address fields in conversion imports return CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE unless on Google's allowlist. Migrate to Data Manager API for rich conversion data ingestion.

References: - Google Ads API Release Notes - Google Ads API Sunset Dates - Google Ads API Rate Limits - Changes to IP Address and Session Attribute Support - Google Ads API v19 Sunset Reminder

⚠️ Meta Marketing API (incl. CAPI)

February 2026 Breaking Change — Graph API v25.0:

The Ads Insights Async report endpoint now includes enhanced error fields: - New fields: error_code, error_subcode, error_message in async report responses - BREAKING: error_code type changed to signed integer (was string/unsigned in some contexts) - Systems expecting the old schema for error parsing may break or produce incorrect error handling

Required Action: - Update error handling logic in meta_operations_integration.py, api_resilience_integration.py, and any module parsing Meta Ads Insights async reports - Ensure error_code is parsed as a signed integer - Add handling for new error_subcode and error_message fields

References: - Meta Business SDK v24.0 Release Notes - Enhanced Error Messaging for Ads Insights Async API - Meta Graph API Changelog

✅ GA4 Analytics Data API (v1)

References: - GA4 Data API Limits and Quotas

✅ Salesforce Marketing Cloud (REST/SOAP)

References: - Salesforce Marketing Cloud API Guide - Salesforce API Limits and Guidelines

✅ Amazon Advertising API

References: - Amazon Ads API Release Notes - Amazon Ads Access Tokens

✅ Google Knowledge Graph Search API

References: - KG Search API Usage Limits

NEW: February 2026 Breaking Changes (Added Feb 12, 2026)

📋 6. Google Ads API — Session/IP Fields Blocked (Feb 2, 2026)

Effective Date: February 2, 2026 Impact: Medium — Conversion import workflows using session attributes or IP addresses

What Changed: - Google Ads API stopped accepting new session-attribute or IP address fields in conversion imports - Existing users with prior session/IP imports are grandfathered (for now) - New attempts return CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE errors - Google is pushing toward the Data Manager API for rich conversion data ingestion

MIZ OKI Impact: - enhanced_conversions_integration.py — Review conversion upload payloads for session/IP fields - value_based_bidding_integration.py — Verify GCLID attribution doesn't send blocked fields

Required Actions: 1. Audit conversion upload payloads for user_ip_address or session fields 2. Remove any new session/IP fields from conversion imports 3. Evaluate Data Manager API as replacement for rich conversion data

Reference: Changes to IP Address and Session Attribute Support

📋 7. Google Ads API v19 Fully Sunset (Feb 11, 2026)

Effective Date: February 11, 2026 Impact: 🔴 CRITICAL — All v19 API calls now FAIL

What Changed: - Version v19 of the Google Ads API officially sunset on February 11, 2026 - Any integrations still calling v19 experience outright failures - Must use v20, v21, or v22

MIZ OKI Impact: - mcp_capability_registry.py — Version firewall already tracked v19 sunset - agent_api_registry.py — Already marked v19 as deprecated with Feb 11 sunset - ⚠️ 19+ files still reference v18 endpoints — These are ALREADY past sunset (Jan 15, 2026) - Affected files include: agent_api_mcp_integration.py, cross_channel_cooldown_manager.py, eshkg_signal_integration.py, knowledge_graph_ingestion_framework.py, enhanced_conversions_integration.py, mcp_connector_registry_v2.py

Required Actions: 1. Update all hardcoded googleads.googleapis.com/v18 URLs to /v22 2. Verify google-ads Python client library version supports v22 3. Run GAQL smoke tests against v22 endpoints

Reference: Google Ads API v19 Sunset Reminder

📋 8. DV360 Targeting Features Sunset (Feb 23, 2026)

Effective Date: February 23, 2026 Impact: High — DV360 Campaign/Insertion Order targeting integrations

What Changed: - Display & Video 360 API and Structured Data Files are sunsetting Campaign and Insertion Order targeting features - After Feb 23: targeting options under Campaign/InsertionOrder via API return 404 - Default generated targeting will be empty in uploads/downloads - Files with unpermitted targeting columns will fail uploads - This aligns with UI removal of these targeting features

MIZ OKI Impact: - ad_budget_reallocation_mvp.py — 11 references to DV360 as DSP execution platform - autonomous_budget_reallocation_mvp.py — Contains DV360Client class implementation - autonomous_marketing_optimization.py — DV360 channel enum - Any DV360 campaign creation or targeting modification workflows

Required Actions: 1. Audit DV360Client for Campaign/IO-level targeting API calls 2. Move targeting to Line Item level (which remains supported) 3. Update Structured Data File templates to remove Campaign/IO targeting columns 4. Test DV360 integrations before Feb 23 cutoff

Reference: Campaign and Insertion Order targeting sunset in DV360

📋 9. Google Merchant API v1beta Discontinued (Feb 28, 2026)

Effective Date: February 28, 2026 Impact: High — Product feed management and shopping campaign workflows

What Changed: - Google's Merchant API v1beta scheduled for discontinuation on February 28, 2026 - All calls must migrate to stable versions (v1 or later) - Product feed workflows will break if still using v1beta endpoints

MIZ OKI Impact: - Check cell15/Cell15.py and ekis/shopify/ for Merchant API references - Any product feed management or shopping campaign workflows

Required Actions: 1. Audit for merchantapi/v1beta or content/v2.1 endpoint usage 2. Migrate to merchantapi/v1 stable endpoints 3. Update product feed upload schemas if needed 4. Test before Feb 28 deadline

Reference: Google Merchant API Latest Updates

📋 10. Meta Graph API v25.0 Error Field Changes (Feb 2026)

Effective Date: Early February 2026 (rolling) Impact: Medium — Ads Insights Async report error handling

What Changed: - Ads Insights Async report endpoint now includes enhanced error fields - New fields: error_code, error_subcode, error_message - BREAKING: error_code type changed to signed integer - Systems expecting old schema for error parsing may fail or produce incorrect error handling

MIZ OKI Impact: - meta_operations_integration.py — Meta ads operations error handling - api_resilience_integration.py — API error parsing and retry logic - api_governance_integration.py — Error rate tracking - Any module consuming Meta Ads Insights async reports

Required Actions: 1. Update error response parsing to handle error_code as signed integer 2. Add handling for new error_subcode and error_message fields 3. Update circuit breaker logic that keys on Meta error codes 4. Test async report error handling with v25 responses

Reference: Enhanced Error Messaging for Ads Insights Async API

1. Meta Ads Insights API Changes

📋 Change Summary

Effective Date: January 12, 2026 Affected Services: All versions of Meta Ads Insights API Impact: High - Automated reporting and BI dashboards

What's Changing

1. Attribution Windows - 7-day and 28-day view-through windows may no longer be returned - Certain historical breakdowns (unique counts, hourly/frequency) are limited - Empty or truncated data returned if dashboards not updated

2. Breakdown Limitations - Unique count metrics restricted - Hourly breakdowns limited - Frequency-based breakdowns deprecated

Current MIZ OKI Implementation

✅ Protected by existing integrations:

⚠️ Required Actions

1. Update Attribution Logic (Priority: HIGH) - Migrate from 7-day/28-day view windows to 1-day view standard - Update AttributionEngine models to use supported windows - Test reporting pipelines with new field availability

2. ETL Schema Updates (Priority: HIGH) - Review dbt models for deprecated metrics - Add null handling for removed breakdown fields - Update BigQuery tables expecting hourly/frequency breakdowns

3. Dashboard Migration (Priority: MEDIUM) - Audit Command Center UI dashboards for deprecated fields - Update charts using unique counts or hourly breakdowns - Add fallback logic for missing metrics

Migration Code Example

# Before (deprecated)
attribution_config = {
    "click_window": "7d",
    "view_window": "7d"  # May not be returned after Jan 12
}

# After (compliant)
attribution_config = {
    "click_window": "7d",
    "view_window": "1d"  # Supported window
}

References

• Meta Developers: Ads Insights API Metric Availability Updates

2. Meta Messenger Recurring Notifications Deprecation

📋 Change Summary

Effective Date: January 12, 2026 Affected Services: Messenger Platform API Impact: Medium - Re-engagement messaging

What's Changing

1. Recurring Notifications Feature → DEPRECATED - Old programmatic message sending outside 24h window will stop working - Must migrate to Marketing Messages on Messenger API

2. New Requirements - Opt-in required for Marketing Messages - Subscriber management logic updates needed - New API endpoints and authentication flows

Current MIZ OKI Implementation

⚠️ Not Currently Implemented: - MIZ OKI does not currently use Messenger Recurring Notifications - No migration required for existing systems

✅ Future Integration Path: - If/when Messenger messaging is added, use Marketing Messages API from the start - Document in messaging_integration.py (future module)

🔵 Recommended Actions (If Needed)

1. Assess Messenger Usage (Priority: LOW) - Confirm no active Messenger notification flows - Document decision to skip Recurring Notifications entirely

2. Future Integration (Priority: PLANNING) - Bookmark Marketing Messages on Messenger API docs - Plan integration using new API from day one

References

• Meta Developers: Marketing Messages - Messenger Platform

3. Google Ad Manager SOAP API Sunset

📋 Change Summary

Effective Date: Rolling sunsets through 2026 Affected Services: Ad Manager SOAP API (multiple versions) Impact: High - Ad serving and inventory management

Sunset Schedule

What's Changing

1. SOAP → REST Migration - Legacy SOAP API versions being retired - Must migrate to REST-based Ad Manager API - Service disruption if not upgraded before expiry

Current MIZ OKI Implementation

⚠️ Status Unknown: - Ad Manager integration not explicitly documented in current modules - Need to audit for any SOAP API usage

⚠️ Required Actions

1. Audit Current Usage (Priority: HIGH) - Search codebase for Ad Manager SOAP API calls - Check if CM360/DV360 integrations use SOAP - Identify version dependencies

2. Plan REST Migration (Priority: HIGH) - Evaluate REST API endpoints for current use cases - Plan migration timeline before Feb 2026 - Update authentication flows

3. Test Migration (Priority: MEDIUM) - Create staging environment with REST API - Validate functionality parity - Run parallel operations before cutover

Migration Command

# Audit for SOAP API usage
grep -r "admanager.*soap\|AdManagerSoap\|v20250[0-9]" miz-oki-adk-agents/
grep -r "dfp.*soap\|DoubleClick" services/

References

• Google for Developers: Deprecation Schedule | Ad Manager SOAP API

4. Google Shopping Content API Shutdown

📋 Change Summary

Effective Date: August 18, 2026 Deprecated: August 18, 2025 Impact: High - E-commerce product feed management

What's Changing

1. Content API for Shopping → SHUTDOWN - Official deprecation: Aug 18, 2025 - Complete shutdown: Aug 18, 2026 - Must migrate to Merchant API

2. Migration Requirements - All integrations must use new Merchant API - Different endpoints, authentication, and schemas - 8-month migration window (already 5 months in)

Current MIZ OKI Implementation

⚠️ Status Unknown: - Product feed management not explicitly documented - Shopping/e-commerce integrations unclear

⚠️ Required Actions

1. Identify Shopping API Usage (Priority: HIGH) - Audit for Content API for Shopping integrations - Check if product feeds are managed via API - Document current Shopping campaigns

2. Plan Merchant API Migration (Priority: HIGH) - Review Merchant API documentation - Map Content API endpoints to Merchant API - Plan schema migrations for product data

3. Execute Migration (Priority: MEDIUM) - Implement Merchant API client - Migrate product feed uploads - Test before Aug 2026 deadline

Migration Audit Command

# Search for Shopping API usage
grep -r "shopping.*content.*api\|ContentAPI\|shopping/v2" miz-oki-adk-agents/
grep -r "merchant_center\|product.*feed" services/

References

• Google for Developers: Release Notes (v2.1) | Content API for Shopping
• Google Merchant Center: Migrate to Merchant API

5. Google Ads API v19 Sunset

📋 Change Summary

Effective Date: February 11, 2026 Impact: ACTIVE - Ensure v21/v22 (v23 scheduled Jan 2026)

Current MIZ OKI Implementation

✅ Already Protected:

API Version Registry (Current)

API_VERSION_REGISTRY = {
    "google_ads": APIVersionInfo(
        api_name="Google Ads API",
        current_version="v22",
        min_supported_version="v19",
        max_version="v22",
        sunset_date=datetime(2026, 2, 11, tzinfo=timezone.utc),
        sunset_version="v19",
        migration_guide_url="https://developers.google.com/google-ads/api/docs/migration",
        deprecation_warning="Google Ads API v19 sunsets February 11, 2026. Upgrade to v21/v22 required."
    )
}

🟢 No Action Required

Current implementation is compliant. Version firewall will alert if any code attempts to use v19 after sunset.

Integration Verification Summary

✅ Verified Integrations

⚠️ Action Items by Priority

🔴 CRITICAL (< 7 Days)

1. Meta Ads Insights API (Jan 12, 2026) - [ ] Update attribution windows to 1-day view standard - [ ] Test reporting pipelines with new field availability - [ ] Update ETL schemas for deprecated breakdowns - [ ] Add null handling for missing metrics

2. Meta Messenger API (Jan 12, 2026) - [ ] Confirm no active Recurring Notifications usage - [ ] Document decision to skip legacy API

🟡 HIGH PRIORITY (< 30 Days)

3. Google Ad Manager SOAP API (Feb 2026) - [ ] Audit codebase for SOAP API usage - [ ] Plan REST API migration if needed - [ ] Test REST API endpoints in staging

4. Google Ads API v19 (Feb 11, 2026) - [ ] Ensure v21/v22 in all production connectors - [ ] Monitor version firewall alerts

🟢 MEDIUM PRIORITY (< 90 Days)

5. Google Shopping Content API (Aug 18, 2026) - [ ] Identify Shopping API usage (if any) - [ ] Plan Merchant API migration - [ ] Implement Merchant API client

Migration Checklist Template

For each API migration:

### [API Name] Migration

- [ ] **Discover**
  - [ ] Audit current usage
  - [ ] Identify affected code paths
  - [ ] Document dependencies

- [ ] **Plan**
  - [ ] Review new API documentation
  - [ ] Map old endpoints to new
  - [ ] Plan schema changes
  - [ ] Estimate effort

- [ ] **Implement**
  - [ ] Create new API client
  - [ ] Update integration code
  - [ ] Add error handling
  - [ ] Write tests

- [ ] **Validate**
  - [ ] Dry-run comparisons
  - [ ] Staging environment tests
  - [ ] Performance benchmarks
  - [ ] Error rate monitoring

- [ ] **Deploy**
  - [ ] Gradual rollout
  - [ ] Monitor metrics
  - [ ] Alert on failures
  - [ ] Document changes

- [ ] **Cleanup**
  - [ ] Remove old API code
  - [ ] Update documentation
  - [ ] Archive legacy configs

Environment Variables & Configuration

New Variables (If Migrations Proceed)

# Meta Marketing Messages API (future)
META_MARKETING_MESSAGES_TOKEN=""
META_MARKETING_MESSAGES_PIXEL_ID=""

# Google Merchant API (if Shopping migration needed)
GOOGLE_MERCHANT_ID=""
GOOGLE_MERCHANT_API_KEY=""

# Ad Manager REST API (if migration needed)
AD_MANAGER_REST_ENDPOINT=""
AD_MANAGER_API_VERSION="v1"

Current Protected Variables

# Already configured and protected
META_ACCESS_TOKEN=""           # v24.0 Marketing API
META_PIXEL_ID=""               # CAPI
GA4_MEASUREMENT_ID=""          # v2 Measurement Protocol
GA4_API_SECRET=""              # MP API Secret
GOOGLE_ADS_API_VERSION="v18"  # Protected by version firewall

Monitoring & Alerts

Recommended CloudWatch/Monitoring Alarms

1. API Version Sunset Alerts - Alert at 90 days, 30 days, 7 days before sunset - Monitor version firewall blocked requests

2. Attribution Field Availability - Alert on sudden drop in metric availability - Monitor null rates in attribution reports

3. API Error Rate Spikes - Alert on 4xx errors indicating deprecated endpoints - Monitor 429 rate limit responses

4. Migration Health - Compare old vs new API response times - Monitor success rates during parallel operations

Next Steps

1. Immediate (This Week) - Complete Meta Ads Insights API attribution migration - Audit Ad Manager SOAP usage - Document Shopping API usage (if any)

2. Short-Term (Next 30 Days) - Execute SOAP → REST migration if needed - Complete ETL schema updates - Deploy monitoring alarms

3. Long-Term (Next 90 Days) - Merchant API migration (if Shopping used) - Quarterly API version audits - Document all platform API versions in registry

Document Control

References

1. Meta Developers: Ads Insights API Metric Availability Updates
2. Meta Developers: Marketing Messages - Messenger Platform
3. Google for Developers: Deprecation Schedule | Ad Manager SOAP API
4. Google for Developers: Release Notes (v2.1) | Content API for Shopping
5. Google Ads API: Migration Guide
6. Meta Graph API Changelog
7. Google Merchant Center: Migrate to Merchant API
8. Google Ads API Release Notes
9. Google Ads API Rate Limits
10. Meta Marketing API Rate Limiting
11. GA4 Data API Limits and Quotas
12. Salesforce Marketing Cloud API Guide
13. Amazon Ads API Release Notes
14. Amazon Ads Access Tokens
15. KG Search API Usage Limits

Status: ✅ DOCUMENTED | ⚠️ ACTION REQUIRED FOR GOOGLE ADS v19→v21/v22 UPGRADE