For the complete documentation index, see llms.txt. This page is also available as Markdown.

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. 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

Last updated

Was this helpful?