V2 to V4 migration

nathan-vandevoort
Wed, 25 Mar 2026 23:11:55 +0000
Help

Hello,

We’ve been using the Frame.io v2 api (via the python SDK) for some time now. Today our users have been unable to get our tools to work. client.teams.list_all() was returning an empty list.

I did some digging and saw there was a new V4 api so I wanted to give that a shot (via the new python SDK). Following the migration guide I added `x-frameio-legacy-token-auth` to the headers so we can continue to use our legacy tokens and now when I run: client.workspaces.index(<user_id>) I get a 401 unauthorized error code. I’m able to get_me().

We have to use the legacy tokens since we currently do not license frame.io through adobe but still through our original plan.

Is there some authorization limitations with the legacy tokens? Is there some other issue I’m not aware of?

import frameio

token = "<token>"

headers = {'x-frameio-legacy-token-auth': 'true'}
client = frameio.Frameio(token=token, headers=headers)

client_data = client.users.show()
account_id = client.users.show().data.id

client.workspaces.index(account_id=account_id) # Raises 401 error.

Thank you for your help!

4 posts - 3 participants