Snippet-only — full fetch unavailable from this environment (tier-1: HTTP 403 on experienceleague.adobe.com, consistent with prior web-refresh runs' 403 pattern against this domain; tier-4: WebSearch snippet accepted).
What changed. Adobe's Data Access API is deprecated as of June 18, 2026. Adobe's guidance directs customers to use the Destinations feature (Flow Service / dataset export dataflows) for exporting data out of Adobe Experience Platform going forward, rather than the Data Access API.
Why it matters for the KG. Two existing Constraint nodes cite the Data Access API by name as the export mechanism they govern:
- constraint.aep-second-gen-data-access-api-200kb — explicitly names "the Data Access API" as the export path for the 200 KB/profile/year second-generation data limit.
- constraint.aep-first-gen-export-500kb — cites export "through the Data Access API or any other means."
A related search snippet also surfaced a September 1, 2025 default end-date Adobe applied to dataset export dataflows created before the September 2024 release — dataflows needed manual end-date extension to keep exporting, which is a separate but related operational detail about the export path's lifecycle.
Limitation. Snippet-only. The exact wording of the deprecation notice, any grace period or sunset timeline for existing Data Access API integrations, and whether the underlying entitlement limits (200 KB, 500 KB) migrate unchanged to the Destinations-based export path are not confirmed from this source. This is drafted as a body-update candidate in evolution-log/2026-08-03/web-refresh.md for the Technical Reviewer — the routine does not modify the two affected Constraint node bodies directly.