> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/web-services/cardholder-web-service.md). # Cardholder web service Support legacy SOAP cardholder integrations and plan a REST API migration. > ⚠️ This is a legacy SOAP Web Service. It is **deprecated in favour of the** [**REST API**](/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-features.md). New integrations should use the REST API. The Cardholder Web Service enables a third-party system to **create, remove, and modify Cardholders** in Command Centre. Modifiable attributes include cardholder details, cardholder authorisation, Personal Data Fields (PDFs), cardholder cards, cardholder competencies, cardholder access, and user code. The full attribute list is in the API documentation, available on request. ## Deprecation Supported but deprecated in favour of the REST API. **v9.10 is the last version that supports it.** ## Security The service is exposed to the internet, so it uses **TLS 1.1 or 1.2**. SSL 2.0 and 3.0 and TLS 1.0 are excluded for known vulnerabilities. Multi-factor: users need **both** Command Centre logon privileges **and** valid certificates. The service can detect a client certificate used by more than one IP address and refuse the connection. ## Use case Let an external source of truth, such as an HR system, drive cardholder, PDF, and access changes into Command Centre automatically, eliminating dual manual entry. Supported on **v7.90 to v9.10**. *** 🔗 **Related** * [REST API - Features](/knowledge-hub/products/cc-software/configure/interface-options/api/representational-state-transfer-rest-api/rest-api-features.md). The successor for this service. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/interface-options/web-services/cardholder-web-service.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.