Set up a Claude Developer Platform connector

Capabilities

The Claude Developer Platform connector syncs the following resources:

Resource	Sync	Provision
API Keys
Organization Roles
Users
Workspaces

Gather Claude Developer Platform credentials

To configure the Claude Developer Platform connector, you need administrator permissions in Claude Developer Platform.

Create an Admin API key

Under the Manage heading, navigate to API Keys > Admin keys and click Create Admin Key.

Enter any name for the key (e.g., C1) and click Add.

You must create an Admin key, not a regular API key. Admin keys have full access to the Admin API and do not have configurable scopes or permissions.

Copy the key and save it securely. You will not be able to view it again.

Configure the Claude Developer Platform connector

Cloud-hosted
Self-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

In C1, navigate to Apps > Connectors and click Add connector.

Search for Claude Developer Platform and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Enter the configuration:

API Key (required): Anthropic Admin API key (starts with sk-ant-admin)

Click Save.

The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Claude Developer Platform connector is now pulling access data into C1.

Follow these instructions to use the Claude Developer Platform connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals.

Resources

Official download center: For stable binaries (Windows/Linux/macOS) and container images.
GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Claude Developer Platform connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

In the Settings area of the page, click Edit.

Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Claude Developer Platform connector deployment:

Secrets configuration

# baton-claude-developer-platform-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-claude-developer-platform-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Claude Developer Platform credentials
  BATON_API_KEY: <Anthropic Admin API key>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-claude-developer-platform.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-claude-developer-platform
  labels:
    app: baton-claude-developer-platform
spec:
  selector:
    matchLabels:
      app: baton-claude-developer-platform
  template:
    metadata:
      labels:
        app: baton-claude-developer-platform
        baton: "true"
        baton-app: claude-developer-platform
    spec:
      containers:
      - name: baton-claude-developer-platform
        image: public.ecr.aws/conductorone/baton-claude-developer-platform:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-claude-developer-platform
        envFrom:
        - secretRef:
            name: baton-claude-developer-platform-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

Check that the connector data uploaded correctly. In C1, click Applications. On the Managed apps tab, locate and click the name of the application you added the Claude Developer Platform connector to. Claude Developer Platform data should be found on the Entitlements and Accounts tabs.

Done. Your Claude Developer Platform connector is now pulling access data into C1.

All versions of this connector are available at dist.conductorone.com.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Claude Developer Platform connector

Capabilities

Gather Claude Developer Platform credentials

Create an Admin API key

Configure the Claude Developer Platform connector

Resources

Step 1: Set up a new Claude Developer Platform connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Claude Developer Platform credentials

​Create an Admin API key

​Configure the Claude Developer Platform connector

​Resources

​Step 1: Set up a new Claude Developer Platform connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Claude Developer Platform credentials

Create an Admin API key

Configure the Claude Developer Platform connector

Resources

Step 1: Set up a new Claude Developer Platform connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector