I was planning on migrating from V2 to V4 ahead of the June 1 deadline and discovered the V4 share API is significantly less capable than V2.
What I had in V2: Automated creation of review links and presentation links with full control — comments on/off, layout, downloads, theme — all via API.
What V4 gives me: POST /shares only accepts downloading_enabled and name. commenting_enabled appears in GET responses but is rejected as “Unexpected field” on both POST and PATCH. Layout, theme, branding, accent color — none of these exist in the API at all. The PATCH endpoint currently rejects every field I’ve tried.
My biggest concern is forcing customers to upgrade while the API is missing features we actively use in production is a bad experience. My team automated and I have 100’s of clients to depend on this system to continue working as it has. I have over 1000 videos in my library that depend on what I had in V2.
Questions:
1. Is there a timeline for making commenting_enabled writable on create/update?
2. Any plans to expose layout, theme, and branding settings via API? 3. Can customers who depend on these features get an extension past June 1 until the new API is truly upgraded without losing V2 features?