Intermittent 401 scope errors on key with "All" permissions — spikes randomly, no config changes

Also getting the error for vector_store.write

The previously implemented fix did not fully resolve the issue for all users, and the team is continuing to work on it. Thank you for your patience while this is being resolved.

Same issue. Still accures

I’m having two types of problems. When making a request to /v1/threads/thread_6****/messages, the error below occurs, but when I send it again after a while, it works correctly without changing the API key:
Authorization failed - please check your credentials

You have insufficient permissions for this operation. Missing scopes: api.threads.write. Check that you have the correct role in your organization (Reader, Writer, Owner) and project (Member, Owner), and if you’re using a restricted API key, that it has the necessary scopes.

This error occurs when I make a request to the assistants, but it also works if I wait a while and run it again; it’s intermittent.

401 You have insufficient permissions for this operation. Missing scopes: api.assistants.write. Check that you have the correct role in your organization (Reader, Writer, Owner) and project (Member, Owner), and if you’re using a restricted API key, that it has the necessary scopes.

Same problem started today. Token recreation didnt work

Many had reported. You can see OpenAI Status Updates on the Issue
https://community.openai.com/t/intermittent-401-scope-errors-on-key-with-all-permissions-spikes-randomly-no-config-changes/1378804/39

Same issue here, of course it’s on the day we’re demoing our project to executives :face_with_symbols_on_mouth:
Time to switch to Anthropic.

Unbelievable for a company that recently raised at a $840BN valuation, not acceptable. To take 48 hours to acknowledge an issue that makes their API unusable. And not get this fixed right away. This is also not the first time this has happened. We spent the weekend integrating with Gemini as a backup to avoid these in the future.

I created an API key for Zapier workflows. It has all permissions. But still I get the error saying:

You have insufficient permissions for this operation. Missing scopes: model.request. Check that you have the correct role in your organization (Reader, Writer, Owner) and project (Member, Owner), and if you’re using a restricted API key, that it has the necessary scopes.

Very similar intermittent scope issues, but mine is on uploading an image to /files

“error”: { “message”: “You have insufficient permissions for this operation. Missing scopes: api.files.write. Check that you have the correct role in your organization (Reader, Writer, Owner) and project (Member, Owner), and if you’re using a restricted API key, that it has the necessary scopes.”, “type”: “invalid_request_error”, “param”: null, “code”: null }, “detail”: { “message”: “You have insufficient permissions for this operation. Missing scopes: api.files.write. Check that you have the correct role in your organization (Reader, Writer, Owner) and project (Member, Owner), and if you’re using a restricted API key, that it has the necessary scopes.”, “code”: null } }

Sharing another update with everyone in this topic.

@RAUWcc, totally get why that error throws you off.

What’s happening here is the API key you’re using likely doesn’t have the model.request scope enabled. That permission is required to actually send requests to models.

Quick thing to try:

  • Create a new API key
  • When setting it up, make sure model capability is set to Request

A few folks have hit this and that usually clears it up.

If it still shows after that, worth opening a ticket at help.openai.com so it can be checked deeper.

Let us know if the new key fixes it, helps others following along too.

-Mark G

has anyone tried it after fix? Does it work?

I’ve been experiencing this issue for several days now. The slow response from OpenAI makes me suspect it may not be as widespread as this thread suggests - though it’s clearly affecting enough of us to be a real problem.

Since there wasn’t much we could do on our end, I took the opportunity to migrate our integration from the Assistants API to the Responses API (the Assistants API is being sunset in August anyway). So far, after several hours on the Responses API, we haven’t seen a single 401 error. It’s a small sample size, but posting in case it helps anyone else unblock while this gets sorted out.

Now I see the next error: “RBAC: access denied“ when trying to delete thread.

Same here i allready created a new api key and it didnt work

Same here:

error listing runs: error, status code: 401, status: 401 Unauthorized, message: You have insufficient permissions for this operation. Missing scopes: api.threads.read. Check that you have the correct role in your organization (Reader, Writer, Owner) and project (Viewer, Member, Owner), and if you're using a restricted API key, that it has the necessary scopes.

Created a new api key and it didnt work

Have been facing the same issue on the moderation api (API is working intermittently then failing)

Hey everyone, The issue has now been resolved. Please let us know, if you are still facing the issue. Thank you!