Cisco Directory Connector website screenshot

Cisco Directory Connector

The Cisco Directory Connector is an on-premises Windows service that synchronizes users and groups from a corporate directory (typically Microsoft Active Directory or LDAP) into Cisco Webex Control Hub. It supports full and incremental sync, attribute mapping, dry-run preview, and scheduled jobs. Programmatic management is via the related Webex People, Groups, and Organizations APIs in Control Hub; modern deployments increasingly use SCIM 2.0 provisioning from identity providers (Azure AD, Okta) as an alternative to the on-premises connector.

Cisco Directory Connector publishes 3 APIs on the APIs.io network: Groups API, Organizations API, and People API. Tagged areas include Active Directory, Directory, Enterprise, Identity Management, and LDAP.

The Cisco Directory Connector catalog on APIs.io includes 1 JSON-LD context.

Cisco Directory Connector’s developer surface includes authentication, developer portal, developer console, getting-started guide, engineering blog, support, and 9 more developer resources.

27.9/100 thin ▬ flat Agent 29/100 agent aware Full breakdown ↓
scored 2026-08-21 · rubric v0.12.0
AccessFreemiumSelf serve⚡ Free to try
4 APIs
Active DirectoryDirectoryEnterpriseIdentity ManagementLDAPProvisioningSCIMSynchronization

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-21 · rubric v0.12.0
Composite quality — 27.9/100 · thin
Contract Quality 5.0 / 25
Developer Ergonomics 7.1 / 20
Access Clarity 7.4 / 20
Operational Transparency 1.0 / 13
Contract Governance 0.0 / 12
Discoverability 7.4 / 10
Agent readiness — 29/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/cisco-directory-connector: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Webex SCIM 2.0 Provisioning

SCIM 2.0 endpoints used by identity providers such as Microsoft Entra (Azure AD) and Okta to provision users and groups into Webex as an alternative to the on-premises Directory...

Cisco Directory Connector Groups API

The Groups API from Cisco Directory Connector — 3 operation(s) for groups.

Cisco Directory Connector Organizations API

The Organizations API from Cisco Directory Connector — 1 operation(s) for organizations.

Cisco Directory Connector People API

The People API from Cisco Directory Connector — 2 operation(s) for people.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

FinOps 1

Cost, billing, and metering signals for API financial operations.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Cisco Directory Connector Context

1 classes · 4 properties

JSON-LD

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Cisco Directory Connector Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Cisco Directory Connector Agentic Access

12 operations · 6 acting

12 operations · 6 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: cisco-directory-connector
url: https://raw.githubusercontent.com/api-evangelist/cisco-directory-connector/refs/heads/main/apis.yml
name: Cisco Directory Connector
tags:
- Active Directory
- Directory
- Enterprise
- Identity Management
- LDAP
- Provisioning
- SCIM
- Synchronization
type: Index
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/cisco-directory-connector.png
access: 3rd-Party
created: '2024-01-01'
modified: '2026-08-19'
position: Consumer
specificationVersion: '0.23'
description: The Cisco Directory Connector is an on-premises Windows service that synchronizes users and groups from a corporate
  directory (typically Microsoft Active Directory or LDAP) into Cisco Webex Control Hub. It supports full and incremental
  sync, attribute mapping, dry-run preview, and scheduled jobs. Programmatic management is via the related Webex People, Groups,
  and Organizations APIs in Control Hub; modern deployments increasingly use SCIM 2.0 provisioning from identity providers
  (Azure AD, Okta) as an alternative to the on-premises connector.
apis:
- aid: cisco-directory-connector:webex-scim
  name: Webex SCIM 2.0 Provisioning
  tags:
  - Identity
  - Provisioning
  - SCIM
  - Standards
  humanURL: https://developer.webex.com/docs/api/v1/scim2-people
  baseURL: https://webexapis.com/identity/scim
  properties:
  - url: https://developer.webex.com/docs/api/v1/scim2-people
    type: Documentation
  - url: https://datatracker.ietf.org/doc/html/rfc7644
    type: Specification
  description: SCIM 2.0 endpoints used by identity providers such as Microsoft Entra (Azure AD) and Okta to provision users
    and groups into Webex as an alternative to the on-premises Directory Connector.
- aid: cisco-directory-connector:cisco-directory-connector-groups-api
  name: Cisco Directory Connector Groups API
  description: The Groups API from Cisco Directory Connector — 3 operation(s) for groups.
  humanURL: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/directoryconnector/wbx_b_directory-connector-guide.html
  baseURL: https://webexapis.com/v1
  tags:
  - Group
  tags_raw:
  - Groups
  properties:
  - type: OpenAPI
    url: openapi/cisco-directory-connector-groups-api-openapi.yml
  - type: Documentation
    url: https://developer.webex.com/docs/api/guides/directory-connector
  - type: Authentication
    url: https://developer.webex.com/docs/integrations
  - type: SDKs
    url: https://developer.webex.com/docs/sdks
  - type: RateLimits
    url: https://developer.webex.com/docs/api/basics#rate-limiting
  - type: Documentation
    url: https://developer.webex.com/docs/api/v1/organizations
  - type: Console
    url: https://admin.webex.com
- aid: cisco-directory-connector:cisco-directory-connector-organizations-api
  name: Cisco Directory Connector Organizations API
  description: The Organizations API from Cisco Directory Connector — 1 operation(s) for organizations.
  humanURL: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/directoryconnector/wbx_b_directory-connector-guide.html
  baseURL: https://webexapis.com/v1
  tags:
  - Organization
  tags_raw:
  - Organizations
  properties:
  - type: OpenAPI
    url: openapi/cisco-directory-connector-organizations-api-openapi.yml
  - type: Documentation
    url: https://developer.webex.com/docs/api/guides/directory-connector
  - type: Authentication
    url: https://developer.webex.com/docs/integrations
  - type: SDKs
    url: https://developer.webex.com/docs/sdks
  - type: RateLimits
    url: https://developer.webex.com/docs/api/basics#rate-limiting
  - type: Documentation
    url: https://developer.webex.com/docs/api/v1/organizations
  - type: Console
    url: https://admin.webex.com
- aid: cisco-directory-connector:cisco-directory-connector-people-api
  name: Cisco Directory Connector People API
  description: The People API from Cisco Directory Connector — 2 operation(s) for people.
  humanURL: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/directoryconnector/wbx_b_directory-connector-guide.html
  baseURL: https://webexapis.com/v1
  tags:
  - People
  properties:
  - type: OpenAPI
    url: openapi/cisco-directory-connector-people-api-openapi.yml
  - type: Documentation
    url: https://developer.webex.com/docs/api/guides/directory-connector
  - type: Authentication
    url: https://developer.webex.com/docs/integrations
  - type: SDKs
    url: https://developer.webex.com/docs/sdks
  - type: RateLimits
    url: https://developer.webex.com/docs/api/basics#rate-limiting
  - type: Documentation
    url: https://developer.webex.com/docs/api/v1/organizations
  - type: Console
    url: https://admin.webex.com
common:
- type: ParentCompany
  url: https://apis.io/providers/webex/
  name: Webex
  x-relationship: product
  x-generated-by: cisco-family:2026-08-19
- type: AgenticAccess
  url: agentic-access/cisco-directory-connector-agentic-access.yml
- type: DomainSecurity
  url: security/cisco-directory-connector-domain-security.yml
- type: Authentication
  url: authentication/cisco-directory-connector-authentication.yml
- type: Portal
  url: https://developer.webex.com
- type: Console
  url: https://admin.webex.com
- type: GettingStarted
  url: https://developer.webex.com/docs/getting-started
- type: Authentication
  url: https://developer.webex.com/docs/integrations
- type: StatusPage
  url: https://status.webex.com
- type: Blog
  url: https://developer.webex.com/blog
- type: Support
  url: https://help.webex.com
- type: Downloads
  url: https://help.webex.com/en-us/article/nivpu1g/Deployment-Guide-for-Cisco-Directory-Connector
- type: TermsOfService
  url: https://www.cisco.com/c/en/us/about/legal/terms-conditions.html
- type: PrivacyPolicy
  url: https://www.cisco.com/c/en/us/about/legal/privacy-full.html
- type: JSONLD
  url: json-ld/cisco-directory-connector-context.jsonld
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-parent: webex
x-relationship: product

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/cisco-directory-connector"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/cisco-directory-connector/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/cisco-directory-connector/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.