Sanity error: ClientError: The mutation(s) failed: mutation failed... Insufficient permissions; permission "create" required

Hello! Everything is connected and everything deploys fine but when I use Shopify to either send a test request or update a product, the Shopify function catches an error. I’m pretty sure Netlify has all the permissions and variables it needs. I’m sure this is something simple but I’m having a hard time debugging this.

Sanity error 4: ClientError: The mutation(s) failed: mutation failed on document "788032119674292900": Insufficient permissions; permission "create" required at onResponse (/var/task/src/node_modules/@sanity/client/lib/http/request.js:27:13) at /var/task/src/node_modules/get-it/lib-node/util/middlewareReducer.js:10:22 at Array.reduce (<anonymous>) at applyMiddleware (/var/task/src/node_modules/get-it/lib-node/util/middlewareReducer.js:9:29) at onResponse (/var/task/src/node_modules/get-it/lib-node/index.js:81:22) at /var/task/src/node_modules/get-it/lib-node/index.js:48:55 at callback (/var/task/src/node_modules/get-it/lib-node/request/node-request.js:57:46) at /var/task/src/node_modules/get-it/lib-node/request/node-request.js:141:14 at DestroyableTransform.<anonymous> (/var/task/src/node_modules/simple-concat/index.js:7:13) at Object.onceWrapper (events.js:420:28) { response: { body: { error: [Object] }, url: '***************************************', method: 'POST', headers: { 'content-type': 'application/json; charset=utf-8', 'content-length': '349', 'x-sanity-shard': '*********************', 'x-served-by': '*************', date: '********************', vary: 'Origin', xkey: 'project-************, project-******************', via: '1.1 google', 'alt-svc': 'clear', connection: 'close' }, statusCode: 403, statusMessage: 'Forbidden' }

[jamesanderegg]

My API key was setup without “READ” settings so I made a new key with the proper permissions.

[jamesanderegg]

@jamesanderegg Did you add a new token on Sanity? Just wanted to know what API key you re-made in. Please let me know. Thank you

@jaynerdominguez I had accidentally set up a token using Deploy Studio rights instead of read and write settings so I deleted my old token and made a new one.