Legacy developer token: GET requests return 200 on V4 but POST returns 401 - write access blocked

Help
,
1

Hey Guys,

Running into a write access issue.

Legacy developer token authenticated on V4 GET endpoints but 401 on POST

My legacy developer token (fio-u-) successfully returns 200 on:
GET /v4/accounts
GET /v4/accounts/{id}/projects

But returns 401 on:
POST /v4/accounts/{id}/folders/{id}/files

Headers used:

  • Authorization: Bearer fio-u-xxx
  • x-frameio-legacy-token-auth: true
  • Content-Type: application/json

Token has all scopes selected including asset.create.
Team plan account on next.frame.io.

Is write access via legacy tokens supported?
If not, what’s the minimum plan/config required?

Thanks for your time.

Cheers,
Liam

2

Hi @LiamC,

Thanks for letting us know about this, sorry to hear you are running into some trouble.

To answer your question, if your account can use legacy tokens for authentication, there isn’t any further limitation based on the type of call you’re making. I can also confirm that there isn’t a specific plan level required to use the API.

All that said, the first thing I’d flag here is that /v4/accounts/{id}/folders/{id}/files is a deprecated endpoint.

This endpoint was replaced by Create file (local upload) and Create file (remote upload). I’m linking the docs for each below for your reference:

Updating your request to use one of those two endpoints is the first thing I’d recommend trying. If you continue to run into this with either of those, please update here and we can continue troubleshooting.

Hope this helps!

3

Thanks @rosiec,

We have taken a look and think the issue might be V4 migration.

I can confirm v4_migrated_at is null on my account. GET requests to V4 work fine with my OAuth token, but all POST/write requests return 401 regardless of endpoint – V4 /files/local_upload and V2 /assets/{id}/children both fail.

Is the incomplete V4 migration the cause? How do I get my account fully migrated?

Thanks for your help Rosie.

Cheers,
Liam