Plugin submission blocked despite approved individual verification

I’m experiencing what appears to be an identity synchronization issue in the plugin submission portal. This appears to be a regression of the verification synchronization issue (#1381183) reported and marked resolved in June. Unlike the earlier reports, this blocks creation of the plugin draft itself.

  • Organization Settings shows Verified → Individual → Approved.
  • I am an Owner of the same organization.
  • /plugins → Create plugin → either With MCP or Skills only displays: “You need a verified developer identity before you can create or upload a plugin.”
  • The supported /plugins?create=1 route produces the same result.
  • In DevTools, GET /v1/dashapi/plugins/identities returns HTTP 200:

{"identities":[]}

This appears inconsistent with the approved verification shown in Organization Settings. Has anyone found a way to get the approved identity synchronized with the plugin identities service? I already have an open support case but have not received a resolution.

Official documentation indicates that approved individual verification should support publishing under the individual’s name.

Setup. Organization Settings → Verifications shows Business: Approved. Individual verification was never started. I am an Owner of the organization, and the Owner preset role includes Apps Management: Write.

Repro. All three paths hit the same wall, and it survives full page reloads:

  • /plugins → Create plugin → With MCP → “You need a verified developer identity before you can create or upload a plugin.”
  • Create plugin → Skills only → same dialog.
  • Navigating straight to /plugins?create=1 → same dialog.

The docs say either track is enough:

“Complete individual verification if you will publish under your own name, or business verification if you will publish under a company name.”

So an approved business verification should let me publish under the company name. It doesn’t get past draft creation.

Here is what I think is happening, and your finding supports it. GET /v1/dashapi/plugins/identities returns {"identities":[]} for me too. That endpoint looks like a separate registry from the org Verifications panel. Approving a verification writes to the panel’s store, but nothing copies the result into the plugin identities service, so the plugins UI asks a registry that was never told. Both tracks fail the same way because the missing piece is the copy step, not the verification.

One more observation that may be the same root. On every load of /plugins, GET /v1/dashboard/organization/permissions returns 401, while the project-scoped /v1/dashboard/projects/{id}/permissions returns 200. On first load this sometimes renders the “ask an organization admin to assign you a role with the api.apps.read permission” empty state for an Owner who has that permission. It clears on a second load. If the identities lookup runs in that same broken org-level auth context, that would explain both symptoms.

Has anyone actually had an approved verification synced into the plugin identities service, through support or otherwise? I’m happy to add my org ID and timestamps to an existing case if that narrows it down.

For whoever finds this thread later: this desync has been reported since April, on both tracks. (I would link these, but new accounts can’t post links — topic IDs given instead.)

  • ChatGPT App submission blocked — “individual verification is not complete” despite Identity Approved (Case 07705870), topic 1379307 — Apr
  • App submission blocked despite approved verification, topic 1380997 — that one cleared on its own after a few days (“It was some sort of strange bug and got fixed automatically”), and the app was later approved
  • Business and individual verification succeeded, but cannot submit, topic 1381436
  • ChatGPT App submission blocked despite Approved business verification, topic 1382668 — business track, same as mine

What is different this time: earlier reports were blocked at final submission. This blocks draft creation, so there is no form to fill and nothing to work around.

I checked the same requests on my account. Both the organization and project permission checks return 200, so the 401 does not reproduce for me. However, /v1/dashapi/plugins/identities still returns 200 with an empty identity list despite my Individual verification showing Approved. This appears to be a plugin identity synchronization issue rather than organization permissions.

Good to know the 401 doesn’t reproduce for you — that rules out my org-level auth theory and narrows this to the verification → identities copy step, which fails the same way on both tracks.

One precedent worth measuring against is topic 1381417. Several people there found the Verifications panel marks Approved a few days before the backend actually finishes — “the settings section marks as ‘confirmed’ a few days too early. The actual confirmation seems to take a few days” — and submission started working on its own. Staff later confirmed a fix had been deployed for that round.

My business verification was approved just over 24 hours ago, so I’m still inside that window. If it hasn’t cleared in another day or two, that would separate a slow sync from a real regression. How long has yours been showing Approved?

I’m opening a support ticket with my org ID and the empty identities response, and will report back here if anything moves.

I’ve been approved for months so that isn’t the case for me.

Any luck on this? I have been facing the same issue.

Nope. Support finally replied and asked me for some info to help diagnose but I haven’t heard anything in a while.

I’m seeing a related issue. Since yesterday, I haven’t been able to access or update my existing plugins. The plugins page loads, but the entries just remain stuck loading. I’ve already opened a ticket with OpenAI Support.

Obviously I’m not happy you’re having the problem too, but it’s useful to know this isn’t isolated to one account. I’m attaching a screenshot of what I’m seeing.

I’ll post again if Support gives me any useful information.

yeah facing similar issue

Individual or business verification should be sufficient. The empty identity response explains the blocker, but we still need to establish why the approved identity is missing. Please add your selected organization/project and a recent request ID or timestamp to your existing Support case if not already provided and please provide the case id here so we can use those information and identify the root cause. Thank you!

I have already provided all of that information in support case 12690933.

I have raised a similar request here, from the chatgpt account we have been trying to make a plugin on - Plugin creation error: Getting you need to be a verified developer before you can create or upload a plugin

Do take a look at it as well. This is the case number for it - 15118347.
I will share organization under that post.

I’ve raised the same issue as well. Support case 15466023

Had the same issue for the past month. Gone around in circles with OpenAI support which has just been a waste of time, Case Number: 15270650

Has anyone managed to figure out how to work around this?

Support reached out to me this weekend and asked for some info.
No updates as of now. Did you hear from them?

Same issue here. Adding the details OpenAI_Support asked for on Sept 20:

- Organization: “Mobiliario” (Individual verification shows Verified in Settings > Organization), project: Default project. I am the Organization Owner.

- Latest reproduction: Oct 6, 2026. GET /v1/dashapi/plugins/identities returns HTTP 200 with {“identities”:[]}. “Upload new version” on my plugin shows Developer identity: “No available identity”.

- Support cases: 15873773 (escalated to a specialist), linked to 12494805 and 11702245 (open since July), plus 16313982.

Side effect worth knowing: my first package was imported with MCP authentication set to “No Auth”, which is locked in the UI. My server uses OAuth, so the tool scan fails with “Unauthorized”. The fix is a new package with oauth_resource in mcp.json, but uploading it is blocked by the same empty identities response. So this bug also blocks fixing an already uploaded plugin, not only new submissions.

I am facing the same issue. I have a personal organization verified. Submitting the plugin always redirects to the settings page with the popup:

Complete identity verification

You need a verified developer identity before you can create or upload a plugin.

Same issue here, adding my case for the collection.

  • Support case: 16126525
  • Account type: Individual verification, status Approved (Settings > Organization > General)
  • Symptom: Plugins > “Upload new or existing plugin” shows “You need a verified developer identity before you can create or upload a plugin”. Continue only leads back to the settings page that shows Approved.
  • Network: GET /v1/dashapi/plugins/identities returns HTTP 200 with {“identities”:}. In the same session GET /v1/dashboard/user/identity_verification returns “status”:“approved”.
  • Reproduced on 4 and 5 October 2026, including incognito and a full sign-out/sign-in.

@OpenAI_Support could you please add this case to the engineering investigation for this issue? Happy to share org and project IDs through the case.

Same issue here, adding the details requested on Sept 20:

  • Individual verification shows Verified in Settings > Organization > General. I am the Organization Owner (single-member org, its own pay-as-you-go billing, not a sub-org).
  • Clicking “Upload new or existing plugin” at /plugins calls GET /v1/dashapi/plugins/identities (HTTP 200, {"identities":[]}), then shows “You need a verified developer identity before you can create or upload a plugin.” The draft upload returns developer_identity_unavailable.
  • Reproduced in two organizations, including a newly created one, and after a full sign-out/sign-in plus incognito (Oct 5-7, 2026).
  • Support case: 16542333. Org and project details are in the case.

@OpenAI_Support could you add this case to the engineering investigation?

I have had the exact issue, reached out to OpenAI customer service (Case Number: 16236108), they sent me a loong email without any action points. So, ended up here to support this ticket on the same bug.