Hi @CharlieAnderson,
Thanks for the helpful documentation. It’s aided me a lot in migrating over to the new API this week. I’m nearing the end of my migration to the V4 API and platform as a whole, so I wanted to share my initial thoughts and feedback while everything is still fresh. Hopefully you can pass this along to the relevant teams for consideration. I’ve verified that I’m not the only person running into most of these, so I imagine this feedback will resonate with other developers in the community too.
API Issues
Guest Commenter Names Not Available via API
There’s currently no way to retrieve guest reviewer/commenter names through the API. If a guest leaves a comment on a review link, their name simply isn’t included in the response. For anyone building notification or reporting workflows around comments, this is a significant gap - we need to know who said what. I’ve already responsed to this in another thread and shared my hacky work around for now. This was in the previous API.
No Way to List Assets Within a Share
There doesn’t appear to be an endpoint to list the assets contained within a share/review link. Being able to programmatically query what’s been shared (and with whom) would be really useful for automation and audit purposes. This was in the previous API.
Start Time Field Doesn’t Reflect Actual File Timecode
The start time field defaults to 00:00:00:00 regardless of the source file’s actual starting timecode. This means if a video’s timecode doesn’t begin at 00:00:00:00, there’s no way to derive the real timecode of a comment through the API. This is a blocker for anyone working in post-production where source timecode matters (which is most of us).
Comment Timestamps Occasionally Off by One Frame
I’ve noticed that comment timestamps are sometimes one frame off from where the comment was actually placed. I can’t identify a consistent pattern — it seems like a rounding error somewhere in the pipeline. It’s a small thing, but accuracy matters when you’re referencing specific frames.
Frontend Issues
Statuses Need to Be Back in the Top Bar
Statuses have been moved out of the top bar and buried within the fields/metadata panel. This is a big step backwards for usability. Clients won’t dig into a menu to set a status, they just won’t use it. And internally, we need to be able to glance at statuses quickly without clicking into anything. The old UI had this exactly right; there was no need to change it.
Version Stacks Don’t Update Dynamically When Created via API
When you create a version stack through the API, the UI doesn’t reflect the change until you manually refresh the page. In V3, the UI would update dynamically. This makes API-driven version management feel broken from the user’s perspective, even though it’s working correctly on the backend.
DELETE Keyboard Shortcut Removed
In the old FrameIO, you could select items and hit Delete to remove them. Now you have to right-click and open a context menu to delete anything. It’s an unnecessary extra step that slows down everyday file management. Please bring the keyboard shortcut back.
Happy to provide more detail on any of these, or help reproduce issues if that’s useful. Overall the V4 platform is shaping up well - these are just the rough edges I’ve hit along the way.
Cheers, Josh