Skip to content
Changelog

Report a bug

Anthropic Administrator integration: operations for AI agents

Anthropic Administrator connects to Type.com as an integration. This page lists the 59 operations documented for Claude and Codex in Type.com: 26 read, 22 write, 11 destructive.

About Anthropic Administrator

The Anthropic Admin API allows programmatic management of organizational resources, including members, workspaces, and API keys.

Categories: Developer Tools & IT

How to connect Anthropic Administrator to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

59 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

59 operations listed.

api keys

  • Read

    List api keys

    List API Keys

    GET /v1/organizations/api_keys

  • Read

    Retrieve api keys

    Get API Key

    GET /v1/organizations/api_keys/{api_key_id}

  • Write

    Update api keys

    Update API Key

    POST /v1/organizations/api_keys/{api_key_id}

compliance settings

  • Read

    Retrieve compliance settings

    Retrieve your organization's Compliance Settings. Compliance Settings is a singleton resource: there is exactly one per organization, addressed without an identifier. The `state` field reflects whether the Compliance API is enabled. An organization with a parent organization reads the state inherited from the parent's configuration.

    GET /v1/organizations/compliance_settings

  • Write

    Update compliance settings

    Update your organization's Compliance Settings. Setting `state` to `enabled` turns on the Compliance API and begins capturing organization activity events. Setting it to `disabled` turns both off. `state` reflects whether the Compliance API is enabled. A request that sets `state` to its current value succeeds and leaves the resource unchanged. A `disabled` request stays in effect until a later `enabled` request or the organization's next provisioning action that enables Access Transparency: enabling Access Transparency also enables the Compliance API, which serves its activity events, so such provisioning (including re-runs) re-enables the Compliance API even after a `disabled` request. Automated provisioning never disables compliance settings.

    POST /v1/organizations/compliance_settings

external keys

  • Read

    List external keys

    List external key configs in the caller's organization. Results are ordered by creation time (newest first). Use the `next_page` cursor from the response to fetch subsequent pages.

    GET /v1/organizations/external_keys

  • Read

    Retrieve external keys

    Retrieve a single external key config in the caller's organization by ID.

    GET /v1/organizations/external_keys/{external_key_id}

  • Write

    Create external keys

    Create an external key config owned by the caller's organization.

    POST /v1/organizations/external_keys

  • Write

    Update external keys

    Partially update an external key config. Omitted fields are left unchanged. `display_name` is always editable. `geo` and `provider_config` cannot be changed once any workspace references this config, because previously encrypted data requires the original key identity to decrypt.

    POST /v1/organizations/external_keys/{external_key_id}

  • Write

    Validate external keys

    Validate an external key config against the customer's KMS. Anthropic performs an encrypt/decrypt roundtrip against the configured KMS key and waits up to 30 seconds for the result. The response status is `success` if the roundtrip succeeded, or `failure` with an error message if it failed or timed out.

    POST /v1/organizations/external_keys/{external_key_id}/validate

  • Destructive

    Delete external keys

    Delete an external key config. The request is rejected if any workspace still references this config.

    DELETE /v1/organizations/external_keys/{external_key_id}

federation / issuers

  • Read

    List federation / issuers

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). List federation issuers in your organization. Archived issuers are excluded unless `include_archived=true`.

    GET /v1/organizations/federation_issuers

  • Read

    Retrieve federation / issuers

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Retrieve a federation issuer by its ID (`fdis_...`).

    GET /v1/organizations/federation_issuers/{federation_issuer_id}

  • Write

    Create federation / issuers

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Register an OIDC issuer that Anthropic will trust for workload identity federation in your organization. The `jwks` field controls how the issuer's signing keys are obtained and takes one of three shapes selected by `type`: `discovery` (resolve keys through OIDC discovery), `explicit_url` (fetch keys from a fixed JWKS URL), or `inline` (provide a static key set). When `jwks.type` is `discovery` and no `discovery_base` is set, the issuer URL must be publicly reachable over HTTPS so Anthropic can fetch the discovery document; for `explicit_url` and `inline` modes the issuer URL is only matched as the JWT's `iss` claim and is not fetched.

    POST /v1/organizations/federation_issuers

  • Write

    Update federation / issuers

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Partially update a federation issuer. Setting `jwks` replaces the full JWKS shape at once. Archived issuers cannot be updated; this returns 400. Create a new issuer instead. Updating an issuer that backs a rule with a scope outside `workspace:developer` or `workspace:inference` requires a Console session.

    POST /v1/organizations/federation_issuers/{federation_issuer_id}

  • Destructive

    Archive federation / issuers

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Archive a federation issuer. Idempotent; re-archiving returns the issuer with its original `archived_at`. Rejected with 400 if any live (non-archived) federation rule still references the issuer; archive those rules first (a rule's issuer cannot be changed), or recreate them against another issuer.

    POST /v1/organizations/federation_issuers/{federation_issuer_id}/archive

federation / rules / rules

  • Read

    List federation / rules / rules

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). List federation rules in your organization. Optionally filter by issuer with `issuer_id`. Archived rules are excluded unless `include_archived=true`.

    GET /v1/organizations/federation_rules

  • Read

    Retrieve federation / rules / rules

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Retrieve a federation rule by its ID (`fdrl_...`).

    GET /v1/organizations/federation_rules/{federation_rule_id}

  • Write

    Create federation / rules / rules

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Create a federation rule owned by your organization. The referenced issuer and the target service account must already exist in the same organization; invalid references are rejected with a 400 error. The workspace reference is validated. Membership is not checked at rule creation: token exchange resolves a single enabled workspace per call and is rejected unless the target service account is a member of that workspace (it is implicitly a member of the default workspace). Rules on well-known shared issuers (GitHub Actions, GitLab, Buildkite, Terraform Cloud, Google) must constrain tenant identity via an identity-bearing claim, a tenant-pinning subject prefix (such as `repo:YOUR_ORG/...`), or a CEL condition referencing one of those identity claims (e.g. `claims.repository_owner`). OAuth callers may only manage rules whose `oauth_scope` is `workspace:developer` or `workspace:inference`; other scopes require a Console session.

    POST /v1/organizations/federation_rules

  • Write

    Update federation / rules / rules

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Partially update a federation rule. `issuer_id` is immutable. `match` and `target` are replaced as whole objects when set. Referenced service accounts and workspaces must exist in your organization; invalid references are rejected with a 400 error. Archived rules cannot be updated; this returns 400. Create a new rule instead. Rules on well-known shared issuers (GitHub Actions, GitLab, Buildkite, Terraform Cloud, Google) must constrain tenant identity via an identity-bearing claim, a tenant-pinning subject prefix (such as `repo:YOUR_ORG/...`), or a CEL condition referencing one of those identity claims (e.g. `claims.repository_owner`). On these issuers the requirement is re-checked on every update; if an existing rule's stored match does not yet constrain tenant identity, any update (even a rename or description change) must also supply a conforming `match` in the same request. OAuth callers may only manage rules whose `oauth_scope` is `workspace:developer` or `workspace:inference`; other scopes require a Console session.

    POST /v1/organizations/federation_rules/{federation_rule_id}

  • Destructive

    Archive federation / rules / rules

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Archive a federation rule. Token exchange through this rule stops immediately. Idempotent; re-archiving returns the rule with its original `archived_at`. Archiving clears the rule's workspace targeting (`workspace_id` and `workspace_ids` are emptied). Tokens already minted before archive remain valid until they expire. OAuth callers may only manage rules whose `oauth_scope` is `workspace:developer` or `workspace:inference`; other scopes require a Console session.

    POST /v1/organizations/federation_rules/{federation_rule_id}/archive

federation / rules / workspaces

  • Read

    List federation / rules / workspaces

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). List workspaces where this federation rule is enabled. Returns all workspace enablements in a single response; the `limit` and `page` parameters are accepted but have no effect, and `next_page` is always `null`. Returns explicit per-workspace enablements only; for rules with `applies_to_all_workspaces` or a legacy single `workspace_id`, check those fields on the rule itself.

    GET /v1/organizations/federation_rules/{federation_rule_id}/workspaces

  • Write

    Add federation / rules / workspaces

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Enable a federation rule for a workspace. Idempotent; re-enabling returns the existing enablement. The rule and workspace must both belong to your organization. Membership of the rule's target service account in this workspace is not checked at enablement: token exchange into this workspace is rejected unless the target is a member (it is implicitly a member of the default workspace). Archived rules are rejected with 400. OAuth callers may only manage rules whose `oauth_scope` is `workspace:developer` or `workspace:inference`; other scopes require a Console session.

    POST /v1/organizations/federation_rules/{federation_rule_id}/workspaces

  • Destructive

    Remove federation / rules / workspaces

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Disable a federation rule for a workspace. Idempotent; succeeds even if the enablement was already removed. OAuth callers may only manage rules whose `oauth_scope` is `workspace:developer` or `workspace:inference`; other scopes require a Console session.

    DELETE /v1/organizations/federation_rules/{federation_rule_id}/workspaces/{workspace_id}

invites

  • Read

    List invites

    List the organization's invites.

    GET /v1/organizations/invites

  • Read

    Retrieve invites

    Retrieve an invite by ID.

    GET /v1/organizations/invites/{invite_id}

  • Write

    Create invites

    Invite a user to join the organization by email. On plans that draw members from a finite pool of purchased seats, the invite automatically consumes a seat from the lowest tier with availability; there is no seat-tier parameter. When no seat is free the request fails with a 400 error rather than purchasing a seat.

    POST /v1/organizations/invites

  • Destructive

    Delete invites

    Delete a pending invite.

    DELETE /v1/organizations/invites/{invite_id}

organization

  • Read

    Retrieve organization

    Retrieve information about the organization associated with the authenticated API key.

    GET /v1/organizations/me

rate limits

  • Read

    List rate limits

    List Messages API rate limits for your organization. Each entry corresponds to one rate-limit group (either a model family or an API-surface category such as the Message Batches API or the web search tool) and contains the set of limiter values that apply to it. When `limit` is omitted, every matching entry is returned in a single page; when `limit` truncates the result, follow `next_page` to fetch the remaining entries.

    GET /v1/organizations/rate_limits

service accounts / service accounts

  • Read

    List service accounts / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). List service accounts in the caller's organization. Results are ordered by creation time, newest first. Use `limit` and the `next_page` cursor to paginate; set `include_archived=true` to include archived service accounts.

    GET /v1/organizations/service_accounts

  • Read

    Retrieve service accounts / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Retrieve a service account by its ID (`svac_...`).

    GET /v1/organizations/service_accounts/{service_account_id}

  • Write

    Create service accounts / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Create a service account. A service account is a named workload identity that federation rules target. `organization_role` is `developer` (default) or `admin`; a rule may only be created or retargeted to grant `org:admin` scope when the target's `organization_role` is `admin`. Creating an `admin`-role service account requires an interactive credential (a user OAuth token or a Console session) — a workload may only create `developer`-role service accounts.

    POST /v1/organizations/service_accounts

  • Write

    Update service accounts / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Update a service account. Only `description` and `organization_role` are mutable; `name` cannot be changed. Archived service accounts cannot be updated; this returns 400. Setting `organization_role` to `admin` (even when unchanged) requires an interactive credential (a user OAuth token or a Console session).

    POST /v1/organizations/service_accounts/{service_account_id}

  • Destructive

    Archive service accounts / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Archive a service account. Idempotent; re-archiving returns the service account with its original `archived_at`. Rejected with 400 if any live (non-archived) federation rule still targets this service account, same as issuer archival; archive those rules first or change their target to another service account.

    POST /v1/organizations/service_accounts/{service_account_id}/archive

service accounts / workspaces

  • Read

    List service accounts / workspaces

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). List the workspaces a service account is a member of. Each entry includes the service account's `workspace_role` in that workspace. Use `limit` and the `next_page` cursor to paginate. When the service account has no explicit default-workspace membership, the implicit (`implicit: true`) membership is returned as the first entry on the first page; with `limit=1` the first page may return up to 2 entries (the implicit entry plus one explicit membership) so a pagination cursor can be derived. Memberships are returned only while the service account is active. Without a `page` cursor, an archived service account returns an empty list. A `page` cursor that does not match an active membership returns a 400 invalid-request error. A cursor stops matching when the membership is removed, the workspace is deleted, or the service account is archived. Restart pagination from the first page to recover.

    GET /v1/organizations/service_accounts/{service_account_id}/workspaces

  • Write

    Add service accounts / workspaces

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Add a service account to a workspace with the given `workspace_role`. Mirror of `POST /workspaces/{workspace_id}/service_accounts`, addressed from the service-account side; both create the same membership. If the service account is already an explicit member of the workspace, its `workspace_role` is replaced with the value supplied here. Archived workspaces return 400. Archived service accounts cannot be added and are rejected.

    POST /v1/organizations/service_accounts/{service_account_id}/workspaces

  • Destructive

    Remove service accounts / workspaces

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Remove a service account from a workspace. Mirror of `DELETE /workspaces/{workspace_id}/service_accounts/{service_account_id}`, addressed from the service-account side. Removal is idempotent (returns 200 even if the membership was already removed). A DELETE against the implicit default-workspace membership returns 200 but is a no-op and the membership persists; deleting an explicit default-workspace row reverts to the implicit `workspace_user` membership. Archived workspaces return 400.

    DELETE /v1/organizations/service_accounts/{service_account_id}/workspaces/{workspace_id}

users

  • Read

    List users

    List the organization's members.

    GET /v1/organizations/users

  • Read

    Retrieve users

    Retrieve a member of the organization by user ID.

    GET /v1/organizations/users/{user_id}

  • Write

    Update users

    Update a member's organization role.

    POST /v1/organizations/users/{user_id}

  • Destructive

    Remove users

    Remove a member from the organization.

    DELETE /v1/organizations/users/{user_id}

workspaces / workspaces

  • Read

    List workspaces / workspaces

    List Workspaces

    GET /v1/organizations/workspaces

  • Read

    Retrieve workspaces / workspaces

    Get Workspace

    GET /v1/organizations/workspaces/{workspace_id}

  • Write

    Create workspaces / workspaces

    Create Workspace

    POST /v1/organizations/workspaces

  • Write

    Update workspaces / workspaces

    Update Workspace

    POST /v1/organizations/workspaces/{workspace_id}

  • Destructive

    Archive workspaces / workspaces

    Archive Workspace

    POST /v1/organizations/workspaces/{workspace_id}/archive

workspaces / members

  • Read

    List workspaces / members

    List Workspace Members

    GET /v1/organizations/workspaces/{workspace_id}/members

  • Read

    Retrieve workspaces / members

    Get Workspace Member

    GET /v1/organizations/workspaces/{workspace_id}/members/{user_id}

  • Write

    Add workspaces / members

    Create Workspace Member

    POST /v1/organizations/workspaces/{workspace_id}/members

  • Write

    Update workspaces / members

    Update Workspace Member

    POST /v1/organizations/workspaces/{workspace_id}/members/{user_id}

  • Destructive

    Remove workspaces / members

    Delete Workspace Member

    DELETE /v1/organizations/workspaces/{workspace_id}/members/{user_id}

workspaces / rate limits

  • Read

    List workspaces / rate limits

    List a workspace's rate limits. By default, returns only the groups and limiter types that have a workspace-level override. With `include_inherited=true`, returns every group with organization-level limits the workspace can see, listing for each the values it inherits from the organization as well as its own overrides. Each value's `source` says which it is. When `limit` is omitted, every matching entry is returned in a single page; when `limit` truncates the result, follow `next_page` to fetch the remaining entries.

    GET /v1/organizations/workspaces/{workspace_id}/rate_limits

  • Write

    Update workspaces / rate limits

    Set or clear rate-limit overrides for one rate-limit group in a workspace. Only the limiter types named in `limits` change: an integer `value` sets that type's override and `null` clears it. Types not named keep their current value. A value above the organization's own limit is stored, but the organization limit still applies, so the lower of the two is enforced. Returns the targeted group's entry with this request applied, in the shape `GET /v1/organizations/workspaces/{workspace_id}/rate_limits` returns. Changes take effect within about an hour.

    POST /v1/organizations/workspaces/{workspace_id}/rate_limits/{rate_limit_id}

workspaces / service accounts

  • Read

    List workspaces / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). List the service accounts that are members of a workspace. Each entry includes the service account's `workspace_role`. Use `limit` and the `next_page` cursor to paginate. Archived workspaces return 400; use `GET /service_accounts/{id}/workspaces` to audit memberships of an archived workspace. The implicit default-workspace membership is not included in this list. Memberships of archived service accounts are omitted from the results.

    GET /v1/organizations/workspaces/{workspace_id}/service_accounts

  • Read

    Retrieve workspaces / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Retrieve a service account's membership in a workspace. Returns the membership record, including the service account's `workspace_role` in this workspace. Archived workspaces return 400. For the default workspace, returns the implicit (`implicit: true`) membership when no explicit membership exists; an explicitly added membership is returned with its assigned role. An archived service account returns 404.

    GET /v1/organizations/workspaces/{workspace_id}/service_accounts/{service_account_id}

  • Write

    Add workspaces / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Add a service account to a workspace with the given `workspace_role`. The role determines what the service account can do in the workspace and which workspace-scoped permissions it can be granted when authenticating through federation. Every service account is already an implicit `workspace_user` member of the default workspace; adding it explicitly assigns a chosen role. If the service account is already an explicit member of the workspace, its `workspace_role` is replaced with the value supplied here. Archived workspaces return 400. Archived service accounts cannot be added and are rejected.

    POST /v1/organizations/workspaces/{workspace_id}/service_accounts

  • Write

    Update workspaces / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Change a service account's role in a workspace. The new `workspace_role` replaces the current one. Only explicit memberships can be updated; to set a role on the implicit default-workspace membership, add the service account explicitly with `POST /workspaces/{workspace_id}/service_accounts`. Archived workspaces return 400. Archived service accounts cannot be updated and are rejected.

    POST /v1/organizations/workspaces/{workspace_id}/service_accounts/{service_account_id}

  • Destructive

    Remove workspaces / service accounts

    **Requires an OAuth access token with the `org:admin` scope**, from `ant auth login --scope org:admin` or a workload identity federation rule; Admin API keys are not accepted. See [Manage WIF with the Admin API](/docs/en/manage-claude/wif-admin-api). Remove a service account from a workspace. Removal is idempotent (returns 200 even if the membership was already removed). A DELETE against the implicit default-workspace membership returns 200 but is a no-op and the membership persists; deleting an explicit default-workspace row reverts to the implicit `workspace_user` membership. Archived workspaces return 400.

    DELETE /v1/organizations/workspaces/{workspace_id}/service_accounts/{service_account_id}

See How connections work for access and permissions, or browse all integrations.

Reference date: October 28, 2026. Anthropic Administrator API docs.