What Is an Anthropic API Organization UUID?

An Anthropic API organization UUID is the unique identifier assigned to your Anthropic Console account (organization) — a string like 12345678-abcd-1234-abcd-1234567890ab that uniquely identifies your org across Anthropic's systems. It's not the same as your API key; it's the parent identifier that your API keys, workspaces, and users all belong to.

If you've landed here because you're setting up billing exports, calling the Admin API, configuring SSO/SCIM, or just poking around the Console settings and found an "Organization ID" field, this is what it refers to. You'll typically need it whenever you're managing the organization itself — not making Claude requests, but administering the account that owns those requests.

Where the Organization UUID Comes From

Every Anthropic Console account is tied to one organization (or more, if you belong to multiple). When the organization is created, Anthropic assigns it a UUID (universally unique identifier) — a randomly generated 128-bit value formatted as five hyphen-separated groups of hex characters. This is a standard identifier format used across most cloud platforms, not something specific to Anthropic.

You can find your organization UUID in the Anthropic Console:

1. Log in to the Console.
2. Go to Settings → Organization (or a similarly named section, depending on your account type).
3. The UUID is displayed alongside your organization name, billing details, and plan tier.

If you have access to the Admin API, you can also retrieve it programmatically by querying organization-level endpoints, since most Admin API responses include the organization ID as a field on returned objects.

What the Organization UUID Is Used For

The organization UUID shows up in a handful of specific contexts:

• Admin API calls. If you're managing workspaces, members, or API keys programmatically through Anthropic's Admin API, requests and responses are scoped to your organization, and the UUID identifies which org you're acting on.
• Usage and cost reporting. When Anthropic reports usage or generates invoices, the organization UUID is the anchor identifier tying spend, token consumption, and workspace activity back to a single billing entity.
• SSO and SCIM provisioning. For enterprise accounts using SAML SSO or SCIM for user provisioning, the organization UUID is often required when configuring the identity provider integration, so Anthropic knows which org a provisioned user belongs to.
• Support tickets. Anthropic support may ask for your organization UUID when troubleshooting account-level issues (billing discrepancies, rate limit questions, access problems), since it's a faster way to locate your account than searching by email or company name.

It's worth being clear about what it is not used for: you don't pass the organization UUID in everyday Authorization headers or in the request body when calling the Messages API. That's handled entirely by your API key. The organization UUID matters at the account-management layer, not the request layer.

Organization UUID vs. API Key vs. Workspace ID

These three identifiers get confused often because they're all strings you copy out of the Console, but they represent different scopes:

• Organization UUID — identifies the entire account. One per organization.
• Workspace ID — identifies a sub-division within an organization, if you use workspaces to separate projects, teams, or environments. An org can have multiple workspaces.
• API key (sk-ant-...) — a credential scoped to make actual requests to Claude, usually tied to a specific workspace within the organization.

Think of it as a hierarchy: organization → workspace → API key. The UUID is the root of that tree, and it rarely changes — it's set once when the organization is created and stays fixed for the life of the account, even if you rename the org or rotate every API key inside it.

Why This Matters for Teams Managing Access

For solo developers, the organization UUID is mostly a curiosity — something you'll see once in the Console and rarely think about again. It becomes more relevant once you have multiple people needing access to Claude under one account, because that's when org-level administration (who has access, how usage is split, how billing consolidates) starts to matter.

If you're managing Claude access for a team and don't want to build your own layer on top of Anthropic's Admin API for tracking per-person or per-project usage, that's exactly the gap SubToAPI fills. Instead of working directly with Anthropic's organization and workspace hierarchy, you generate scoped sub_live_... API keys per application or team member from a single dashboard, with usage metadata attached to each request. You get the practical benefit of organization-level visibility — who's using what, how much it costs — without needing to script against the Admin API yourself. Check the pricing page for plan details, or read the quickstart to see how key issuance works.

Keeping Your Organization UUID Secure

The organization UUID by itself isn't a secret in the same way an API key is — it doesn't grant access to make requests or spend money. But it does identify your account, and it can be used in phishing or social-engineering attempts (someone claiming to be Anthropic support referencing your real org UUID to seem legitimate). Treat it as identifying information, not a credential:

• Don't post it publicly if you can avoid it, though leaking it alone isn't a security incident.
• Never confuse it with an API key when configuring integrations — pasting the org UUID where a key is expected will simply fail authentication, but it's a common copy-paste mistake worth double-checking.
• If you suspect any organization-level compromise (not just a leaked key), rotate all API keys and review Console access logs rather than assuming the UUID itself needs to change — it generally can't be changed anyway.

Questions

Is the organization UUID the same as my API key? No. The API key (sk-ant-...) is a credential used to authenticate requests to Claude. The organization UUID identifies the account that owns those keys and is used mainly for admin, billing, and support purposes — not for making Messages API calls.

Can I have more than one organization UUID? Yes, if you belong to multiple Anthropic Console organizations — for example, a personal account and a company account — each one has its own distinct UUID, and you switch between them in the Console.

Do I need the organization UUID to make Claude API requests? No. Standard requests to Anthropic's Messages API only require your API key in the Authorization header. The organization UUID is relevant for Admin API calls, SSO/SCIM setup, and account-level support, not day-to-day inference calls.