What does 'No such organization' mean in the OpenAI API?

The OpenAI API error 'No such organization' (HTTP 401) occurs when the organization ID you're passing in the OpenAI-Organization header (or the OPENAI_ORG_ID environment variable) doesn't match any organization that your API key has access to. This is most commonly caused by using an org ID from a different OpenAI account, having been removed from the organization, or passing a project ID where an org ID is expected.

Where do I find my OpenAI organization ID?

Your organization ID is available at platform.openai.com/settings/organization. It starts with 'org-'. Do not confuse this with a project ID (which starts with 'proj_') or your account ID. The organization ID is used in the OpenAI-Organization header and the OPENAI_ORG_ID environment variable.

Do I need to pass an organization ID in every OpenAI API call?

No. The OpenAI-Organization header is optional. If you omit it, the API uses the default organization for your API key. Most developers only need to pass it if they belong to multiple organizations and need to specify which one's quota to use. If you're getting organization errors and don't need to target a specific org, the fastest fix is to remove the OpenAI-Organization header entirely from your requests.

What is the difference between an OpenAI organization ID and a project ID?

An organization ID starts with 'org-' and identifies an OpenAI organization (a billing and membership group). A project ID starts with 'proj_' and identifies a specific project within an organization. The OpenAI-Organization header takes an organization ID. If you pass a project ID in the OpenAI-Organization header you will get an error. To scope requests to a project, use the OpenAI-Project header instead.

OpenAI API "No such organization" error: 5 causes in diagnostic order

The OpenAI API returns a "No such organization" or organization-not-found error when the organization ID in your request doesn't match what your API key is authorized to use. This is an authentication-adjacent error — your key might be valid, but the org context you're providing isn't. This page covers the five causes in order and how to fix each.

The 30-second fix

Fastest fix: remove the OpenAI-Organization header entirely. It's optional — omitting it uses your key's default org.
If you need a specific org: get the correct ID from platform.openai.com/settings/organization — it starts with org-.
Don't mix up IDs: org IDs start with org-; project IDs start with proj_. They go in different headers.

What the error looks like

HTTP/1.1 401 Unauthorized
{
  "error": {
    "message": "No such organization: org-XXXXXXXXXXXX.",
    "type": "invalid_request_error",
    "param": null,
    "code": "invalid_organization"
  }
}

The error code is invalid_organization. You may also see variants like "The requesting API key is not a member of organization org-XXXX" if the key exists but isn't in that org. In the OpenAI Python SDK this raises an openai.AuthenticationError (despite being logically a permissions issue).

Cause 1: Wrong organization ID — most common

The most frequent cause is having an org ID from a different OpenAI account in your environment variables or configuration, often copied from a tutorial, a teammate's setup, or a previous job. Your API key is only valid for organizations it belongs to — it cannot be used with another organization's ID even if both IDs are technically valid.

How to get the correct org ID:

Go to platform.openai.com/settings/organization
The organization ID is shown as "Organization ID" — it starts with org-
If you belong to multiple organizations, switch between them via the dropdown in the top-left of the platform UI to see each org's ID

Fix: update your OPENAI_ORG_ID environment variable or OpenAI-Organization header to match the org ID from your platform account. Or remove the org specification entirely to use the default.

Cause 2: API key not a member of the specified organization

Each OpenAI API key is tied to a specific user account. If your user account was removed from the organization, or if you're using a personal key with an enterprise org ID, the key won't have access.

This commonly happens when:

An employee is offboarded but their locally-stored env vars still reference the company org ID
You created a personal key and are trying to use it with a company org that only allows keys generated by org members
You joined a new organization and are still using a key tied to your old org

How to check: at platform.openai.com/api-keys, look at which organization each key belongs to. The key and the org ID in your request must match.

Fix: generate a new API key while logged in and viewing the correct organization context. Or have an org admin confirm that your user account is still a member.

Cause 3: Project ID in the organization header

OpenAI distinguishes between organization-scoped and project-scoped access. The OpenAI-Organization header takes an org- prefixed ID. The OpenAI-Project header takes a proj_ prefixed ID. If you pass a project ID where an org ID is expected, you get an organization-not-found error.

# Wrong — project ID in org header
headers = {
    "Authorization": "Bearer sk-...",
    "OpenAI-Organization": "proj_abc123xyz"  # This is a project ID, not an org ID
}

# Correct — project ID in project header
headers = {
    "Authorization": "Bearer sk-...",
    "OpenAI-Project": "proj_abc123xyz"
}

Fix: if you're using project-based API keys (keys that start with sk-proj-), use the OpenAI-Project header for the project ID, and either omit the OpenAI-Organization header or set it to your org's org- ID.

Cause 4: Organization account deactivated or suspended

If the OpenAI organization has an overdue payment, has been suspended for a policy violation, or was closed, all API keys belonging to that org will return organization-related errors.

How to check: log in to platform.openai.com as an owner of the organization and check billing status. A billing or suspension banner will typically be visible at the top of the platform dashboard.

Fix: resolve the billing or policy issue through the OpenAI platform. If the org was closed, you'll need to either create a new org or use a different org that your account belongs to.

Cause 5: Environment variable not loaded

The OPENAI_ORG_ID environment variable is read at SDK initialization time. If the variable was set after the Python process started, or if the .env file wasn't loaded, the SDK may silently use an empty or stale value that results in an invalid org ID being sent.

# Python: confirm the env var is set before initializing the client
import os
print(os.environ.get("OPENAI_ORG_ID"))  # Should print org-XXXX or None (not an empty string)

from openai import OpenAI
client = OpenAI(
    api_key=os.environ.get("OPENAI_API_KEY"),
    organization=os.environ.get("OPENAI_ORG_ID")  # Can be None — OK, means use default
)

Passing organization=None is safe — the SDK omits the header. Passing organization="" (empty string) may send a malformed header depending on SDK version.

Fix: print os.environ.get("OPENAI_ORG_ID") immediately before the client is initialized to confirm what value is actually being used. If it's wrong, fix the env var source (shell profile, .env file, CI/CD secret) rather than hardcoding the value.

The fastest fix: remove the org header entirely

If you don't have a specific reason to target a particular organization, remove the OpenAI-Organization header and the OPENAI_ORG_ID environment variable. The OpenAI API uses your key's default organization automatically, and the error disappears without any other changes.

This is particularly useful in development and testing environments where the org context doesn't matter.

Last updated June 8, 2026. OpenAI's organization and project structure has changed over time — verify header names and ID formats against the current OpenAI API documentation.