Migration API authorization for "Publisher" user roles?

Developing with Prismic
1

Hi! I'm seeking some clarity on the relationship between the Migration API and user roles.

Expected behavior:
A user with a Publisher role should be able to use the Migration API with their user session token to edit a document.

Actual behavior:
The Migration API works well with a user session token for an Administrator user, but errors with a "401 Unauthorized" error when using a user session token for a Publisher role.

I noticed this line in the Migration API Technical Reference:

This feature is in beta and requires an access key
Admin users can try the Migration API using one of the following demo ke

Will the Migration API eventually support roles other than Administrator?

In the meantime, is it best to use a permanent token instead of user session token?

Thanks in advance for any insights here!

2

Hi @cords ,

Thanks for reaching out!

You’re correct that the Migration API currently requires an access key and is in beta. At this time, only Administrator users can authenticate with a user session token, which is why a Publisher role is receiving a 401 Unauthorized error.

As for future support for other roles, we don’t have an official update yet, but we appreciate the feedback and will share it with the team.

In the meantime, using a permanent access token is the recommended approach if you need to make updates via the Migration API. This ensures the necessary permissions are in place.

Let us know if you have any further questions!