Security requirements changed for GET /marketing/v3/campaigns/{campaignGuid}/reports/revenue

What changed

Security requirements changed for GET /marketing/v3/campaigns/{campaignGuid}/reports/revenue Affected surface: GET /marketing/v3/campaigns/{campaignGuid}/reports/revenue. Detected at Thu, 16 Apr 2026 14:53:44 UTC UTC.

Diff

{
  "current_value": [
    {
      "oauth2": [
        "campaigns-revenue-pro",
        "revenue-attribution-read"
      ]
    }
  ],
  "path": "GET /marketing/v3/campaigns/{campaignGuid}/reports/revenue",
  "previous_value": [
    {
      "app_cookie": [
        "campaigns-revenue-pro",
        "revenue-attribution-read"
      ]
    },
    {
      "hapikey": null
    },
    {
      "internal_cookie": [
        "campaigns-revenue-pro",
        "revenue-attribution-read"
      ]
    },
    {
      "oauth2": [
        "campaigns-revenue-pro",
        "revenue-attribution-read"
      ]
    },
    {
      "shhkey": null
    }
  ]
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Recommended action

Re-check your auth setup against the provider's current docs. Auth changes typically require config updates, not code changes.