> 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/visitor-management-web-service.md).

# Visitor management web service

Support legacy SOAP visitor management 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 Visitor Management Web Service enables a third-party system to **create visits and visitors** in Command Centre.

## Deprecation

Supported but deprecated in favour of the REST API. The same functions exist in the **8.50 REST API**, except **Mark Visitor (Signed In, Offsite, Onsite)**, which was added in the **8.90 REST API**.

## Use case

A calendar or appointment solution (scheduling appointments, booking resources, notifying guests) integrates with Command Centre to assign visitors access if required, and **pre-registers** them so they can use the **Gallagher Visitor Management Kiosk** to sign in and mark themselves onsite.

Supported on **v7.90 to v8.80**.

***

🔗 **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/visitor-management-web-service.md?ask=<question>&goal=<user_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.