Connect & Integrate Anthropic

Last updated: July 22, 2026

Introduction

This guide explains how to connect YeshID to your Anthropic organization (the platform behind Claude, managed at console.anthropic.com). The connection uses Anthropic's Admin API, so it works with your organization account — not with an individual Claude.ai chat account.

Once connected, YeshID uses your Anthropic Admin API key to import and keep an up-to-date inventory of your organization, including:

  • Organization users

  • Workspaces and workspace members (with their workspace roles)

  • API keys and pending invites

  • Cost / spend data (fed into the YeshID Cost Tracker)

Note on scope: The Anthropic Admin API connector is read-only inventory + cost sync. It imports and synchronizes the items above, but it does not create, deactivate, or delete Anthropic users as part of onboarding/offboarding tasks. If you need automated user lifecycle (create / deactivate / delete), see Alternative: Automated user lifecycle via SCIM at the end of this guide.

Prerequisites

  • You must be an admin/owner of your Anthropic organization so you can create an Admin API key.

  • You need admin access in YeshID to add and connect applications.

Steps

1. Create an Admin API key in Anthropic

  1. Sign in to the Anthropic Claude Console.

  2. Go to Settings → Organization.

  3. Create a new Admin API key.

  4. Copy the key. A valid Admin API key starts with sk-ant-admin.

 Important — use an Admin key, not a standard API key. The most common setup issue is pasting a regular Claude API key instead of an Admin API key. Only keys that begin with sk-ant-admin can read organization users, workspaces, members, and invites. Standard keys (sk-ant-… without admin) will not work for this connection.

For more detail, see Anthropic's Admin API documentation.

2. Add Anthropic as an application in YeshID

  1. In YeshID, go to the Connect & Integrate page.

  2. Find Anthropic in the application catalog (or add it as a new application if it isn't already in your list).

  3. When prompted, choose the Admin API setup option.

3. Paste your Admin API key and connect

  1. In the Anthropic setup screen, paste the Admin API key you created in Step 1 into the API key field.

  2. Save / connect.

YeshID will use the key (sent as the x-api-key header) to run an initial import. After connecting, you'll see your Anthropic users, workspaces, workspace members, API keys, and invites synced into YeshID, and spend data flowing into the Cost Tracker.

Optional: Add a Claude API key for Managed Agents inventory

The Admin API key covers all standard org inventory above. If your organization uses Managed Agents and you'd like YeshID to inventory those resources too, you can optionally add a standard Claude API key:

  1. In the Claude Console, go to API Keys and create a standard Claude API key.

  2. In the Anthropic setup screen in YeshID, paste it into the Claude API Key field (this field is optional).

Adding a Claude API key expands the imported inventory to include: agents, tools, MCP servers, environments, sessions, deployments/runs, vault credential metadata, and memory stores.

This is an addition, not a replacement — it does not replace the Admin API key, which is still required for the core connection.

FAQ / Troubleshooting

My key isn't working / the connection fails. The most common cause is using a personal or standard API key instead of an Admin API key. Verify your key starts with sk-ant-admin and was created from Settings → Organization in the Claude Console — not from the personal API Keys section.

Can YeshID create or remove Anthropic users automatically during onboarding/offboarding? Not through the Admin API connector — that connection is read-only (import + cost). For automated user lifecycle, use the SCIM option below.

Does this work with my Claude.ai (ChatGPT-style chat) account? No. This integration is for the Anthropic organization platform, not an individual Claude.ai chat login. You need organization admin access to create the Admin API key.

Alternative: Automated user lifecycle via SCIM (WorkOS)

If you need YeshID to create, deactivate, and delete Anthropic users (and manage group membership) as part of onboarding/offboarding, connect Anthropic through SCIM via WorkOS instead of (or in addition to) the Admin API key.

This is a separate connection type. It uses Anthropic's SCIM directory (provisioned through WorkOS) and a Bearer Token, rather than the sk-ant-admin Admin API key.

What SCIM supports

Unlike the Admin API connector, the SCIM connection supports full user lifecycle and group management:

  • Create User

  • Get User / Update User

  • Activate User / Deactivate User

  • Delete User

  • Import Users

  • Import Groups

  • Add to Group / Remove from Group

Before you begin

  • You are an Anthropic Org Admin, and your plan includes SCIM (Enterprise).

  • You have access to the WorkOS Dashboard.

Step-by-step

1. Create a WorkOS SCIM directory

  1. In WorkOS, go to Organizations ▸ Directory Sync and click Configure manually.

  2. Choose Custom SCIM v2.0 and create the directory.

2. Copy your SCIM base URL

  1. Open the directory's Directory details and locate the Endpoint URL (the SCIM base).

  2. Copy the value.

  3. In YeshID's Anthropic SCIM setup screen, paste it into the API Base URL field.

3. Copy the Bearer Token

  1. On the same WorkOS Directory details page, copy the Bearer Token.

  2. In YeshID, paste it into the Bearer Token field.

4. Save

Click Save. YeshID tests the connection and begins importing users.

For help creating the directory in WorkOS, see the WorkOS SCIM documentation.