Retail plan — 403 Forbidden on /v4/accounts and /v2/assets/:id/comments

1

I’m on a retail (personal) Frame.io plan, trying to read comments on my own files via the API using a developer token from developer.frame.io.

  • GET /v4/me → works (200)
  • GET /v4/accounts → 403 Forbidden (with x-frameio-legacy-token-auth: true header, all scopes enabled)
  • GET /v2/assets/:id/comments → 403 Forbidden

Support confirmed a linked-Adobe-ID issue was fixed on their end, but I still get the same 403 after refreshing and generating a new token. They mentioned retail accounts have limited API support scope.

Is comment-reading API access simply unavailable on retail plans, or is there a specific scope/setup I’m missing?

2

Hi @Oleksandr

Comment reading is available on retail plans, so this is likely related to the request.

One thing to note is that if your account is on V4, you won’t use Legacy routes like /v2/assets/:id/comments. Instead you’ll want to make your requests to the V4 equivalent,
/v4/accounts/:account_id/files/:file_id/comments (endpoint docs can be found here)

First thing to try:

Go to this page of our docs, log in to the account you’ve been testing with, then hit ‘Send request’

If you’re able to hit that endpoint successfully from that console, that helps narrow down the cause quite a bit.