Behance API v2 Deprecation: Missing Programmatic Access for Portfolio Data

Context

Behance's public REST API v2 was deprecated on 2020-11-16, with all endpoints now returning 410 Gone. Adobe has not released a successor API, GraphQL interface, or documented migration path. OAuth 2.0 scopes previously tied to the API ("user", "projects", "collections") are no longer grantable in the Adobe Developer Console, and existing tokens cease functioning once they expire.

Constraint

Third-party integrations that need to read public project metadata — such as portfolio sync tools, analytics dashboards, or cross-platform showcase widgets — have no supported programmatic pathway. The Creative Cloud desktop and Express apps publish to Behance using internal, undocumented endpoints that are not exposed to external developers. HTML scraping or browser automation violates Behance Terms of Use §3.2 and risks WAF blocks.

Open Questions

1. Is there a planned private beta or partner program that would restore read-only access to public project data for approved integrations?
2. Can Adobe confirm whether a future API will support webhook notifications for project updates or comments, a capability that was absent in v2?
3. What is the recommended compliance strategy for existing integrations that currently rely on scraping while awaiting an official replacement?