How to Find Your Claude API Key: A Quick Guide
If you're looking for your Claude API key, it lives in the Anthropic Console under Settings → API Keys. You need an Anthropic account with billing set up (or free trial credits) to generate one, and the key itself is only shown once, in full, at creation time.
If you already generated a key and lost it, you can't retrieve the original value again — Anthropic doesn't store or display it after creation for security reasons. You'll need to revoke the old key and create a new one. This is standard practice for API providers and applies the same way to services like SubToAPI.
Step-by-Step: Finding Your Key in the Anthropic Console
- Go to console.anthropic.com and log in with the account tied to your organization.
- Click Settings in the left sidebar, then API Keys.
- If you've already created a key, you'll see a list with names, creation dates, and partial identifiers (something like
sk-ant-api03-...xxxx) — but not the full secret. - To get a usable key, click Create Key, name it something meaningful (e.g. "production-backend" or "staging-test"), and copy the full string immediately. It won't be shown again.
If this is your first time here and the API Keys page is empty, you don't have a key yet — you'll need to generate one following the steps above.
Common Reasons People Can't Find Their Key
- They're looking in the wrong account. Claude.ai (the chat subscription) and the Anthropic Console (API access) are separate systems with separate logins, even if you use the same email. Having a Claude Pro or Max subscription does not automatically give you an API key.
- They don't have console access. If you're on a team and someone else set up billing, only account owners/admins can view or create keys by default. Ask whoever manages the org to add you as a member with the right permissions.
- The key was revoked. Keys can be deactivated by an admin, by hitting a security flag, or manually. A revoked key stops working immediately and won't reappear in the list as active.
- They're confusing it with an organization ID or workspace ID. Those are separate identifiers (
org-...) used for request routing, not authentication.
What the Key Actually Looks Like
A Claude API key from Anthropic starts with sk-ant-api03- followed by a long random string. You pass it in the x-api-key header (not Authorization: Bearer) when calling the Messages API directly:
curl https://api.anthropic.com/v1/messages \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "content-type: application/json" \
-d '{
"model": "claude-sonnet-4-5",
"max_tokens": 1024,
"messages": [{"role": "user", "content": "Hello"}]
}'Store it as an environment variable, never hardcode it in source, and add it to your .gitignore'd .env file. Treat it exactly like a database password.
If You Only Have a Claude Subscription, Not API Billing
This is the most common source of confusion behind this search. A lot of people have Claude Pro or Max for the chat interface but no separate API billing account, and they assume there's a hidden key somewhere in their subscription settings. There isn't — Anthropic's consumer subscriptions and API billing are intentionally decoupled, partly because API usage is metered per token and can spike in cost in a way a flat subscription can't.
If you want to build something (an app, an internal tool, an automation) using the model access you're already paying for, without setting up separate API billing and juggling raw usage-based invoicing, SubToAPI turns your existing Claude access into a standard HTTPS API. You get an application key in the format sub_live_..., generated from your SubToAPI dashboard, that works with normal REST calls:
curl https://api.subtoapi.app/v1/messages \
-H "Authorization: Bearer $SUBTOAPI_KEY" \
-H "content-type: application/json" \
-d '{
"model": "claude-sonnet-4-5",
"max_tokens": 1024,
"messages": [{"role": "user", "content": "Hello"}]
}'Finding this key later is simpler too — it's in your SubToAPI dashboard under API Keys, same place every time, with support for streaming responses, tool use, and per-key usage metadata so you can see exactly what each application is consuming. Plans start at Solo (€9), with Team (€19/seat) and Scale (€49/seat) tiers if you need multiple seats or higher limits, and there's a free trial at /signup if you want to test it before committing.
Rotating a Key You Already Have
Whether you're using Anthropic's console or SubToAPI, the rotation process is the same pattern:
- Generate a new key first.
- Update your app/environment to use the new key.
- Confirm the new key works in production.
- Revoke the old key.
Doing it in that order avoids downtime. Revoking first and generating second means your app is dead in the water until the new key propagates.
Where to Go Next
- Anthropic's own docs cover the raw Messages API format if you're calling it directly.
- If you're setting up a new integration from scratch and want a walkthrough, /docs/quickstart covers getting a SubToAPI key generated and making your first request in a few minutes.
- For details on request/response shapes, see /docs/messages, and for streaming setups, /docs/streaming.
FAQ
I have Claude Pro — where's my API key? There isn't one automatically. Claude Pro/Max subscriptions and API access are separate products with separate accounts and billing. You either need to set up Anthropic API billing directly, or use a service like SubToAPI that turns your existing subscription into API access without a second billing setup.
I lost my Claude API key — can I see it again? No. API keys are shown in full only once, at creation. If you've lost it, revoke it in the console and generate a replacement — update any apps using the old key before revoking to avoid downtime.
Why can't I find the API Keys page in the Anthropic Console? You likely don't have admin/member permissions on the organization, or you're logged into the wrong account. Confirm you're using the account tied to API billing (not just claude.ai), and ask an org admin to grant you access if needed.