Patch comment forbidden

Help
1

I’ve built an automation to get frame.io comments from the API using the front browser window’s URL to get the asset ID, and then import the comments onto my DAW timeline.

I’d like to also mark the comments as ‘completed’ after they are successfully imported. This worked well during my testing phase, on comments I made myself, but updating a comment left by a real world other frame.io user (on an asset in my workspace) fails with a 403 - Forbidden error.

I can mark the comment as completed in the browser logged in with the same credentials as I am when receiving the error in the API.

2

hi @hc-evan can you provide a bit more detail about the issues you’re facing here? Is it failing when someone who is not logged into Frame.io marks a comment as complete? Aka an anonymous users marks it complete in a share?

FWIW if you are using ProTools, SoundFlow has a native V4 integration built in (and I believe it comes standards with ProTools).

3

@CharlieAnderson

  • I’m getting the 403 Forbidden error when I try to mark a comment as complete via the https://api.frame.io/v4/accounts endpoint.
  • Comments created by the same user as the API is authenticated as can be marked as completed, but it seems like I can’t mark any comments as completed that were created by any other user.
  • As far as I can tell, the mark as complete option is grayed out for anonymous users viewing the share.
  • I am using Pro Tools, but don’t care to subscribe to SoundFlow. The Soundflow version bundled with Pro Tools is very basic and does not included the Frame.io integration.
4

Got it thanks for the info, will attempt to reproduce on my end so I can log a ticket if needed. Will let you know if I need any follow up info in my testing!

Edit: Can confirm I get a 403 as well, logging a ticket. Thanks for flagging @hc-evan

1 Like
5

Hi there! This feature request or issue is now available/resolved and deployed to production! If this message comes on a Friday, this will be available the next business day (Monday). Please reach out to the team here on the forums if you have any questions!

(this is an automated message)

6

@hc-evan FYI this was fixed in our current sprint, so just wanted you to test and see if it resolved your issue.

1 Like
7

confirmed it’s now working! thanks so much

1 Like