--- title: Siemens Sipass slug: acs-sipass createdAt: 2026-05-12T03:03:56.000Z --- # Integration Guide ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/UmnSHA5bXOzQdIWZPPOzo_siemens-sipass-splash-card.png" size="60" width="780" height="310" position="flex-start" alt="Siemens" sha="f9d0aaebef3d14535a18a3e2a6169c3403fcba7a" initialPath="/assets/integration-guide/siemens-sipass/siemens-sipass-splash-card.png" githubPath="docs/assets/integration-guide/siemens-sipass/siemens-sipass-splash-card.png" showCaption="false"} :::hint{type="info"} This integration connects Sine with Siemens Sipass, allowing visitor and access data to be shared between the two systems for streamlined access control management. It enables sites using Sipass to align visitor management workflows with existing physical security infrastructure. This guide is intended for system integrators and IT administrators responsible for configuring and maintaining the connection between Sine and Sipass. ::: # Overview Sine connects with Siemens SiPass to automatically provision and revoke visitor access credentials as visitors check in and out. This integration supports Sine QR Code credentials, which are assigned via QR codes printed on visitor badges or sent via SMS, and Physical Assets credentials, which let you manage physical cards, such as HID proximity cards, as assets in Sine and assign them to visitors on check-in. # How It Works Sine integrates with Siemens Sipass via an on-premise adaptor, synchronizing visitor credential data between the cloud-based Sine platform and the Sipass access control system to automate credential provisioning and revocation. ## QR Code Visitors are issued a Sine QR Code credential that can be scanned at compatible readers connected to Siemens Sipass. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/YdavmVeZ4xlK7HLxdPeAY_cloud-to-onprem-qrcode-flow-with-adaptor.png" size="120" position="flex-start" alt="cloud-to-onprem-qrcode-flow-with-adaptor" sha="c306e7b6e5641314f22c9f9f4d18ed018a038b09" initialPath="/assets/integration-guide/siemens-sipass/cloud-to-onprem-qrcode-flow-with-adaptor.png" githubPath="docs/assets/integration-guide/siemens-sipass/cloud-to-onprem-qrcode-flow-with-adaptor.png" showCaption="false"} **Check-in Flow:** ::::WorkflowBlock :::WorkflowBlockItem The visitor initiates check-in through Sine, using a kiosk, the mobile app, a web form, or a printed QR poster. ::: :::WorkflowBlockItem Sine provisions a unique QR code credential, scoped to the visitor's assigned access groups for the duration of their visit. ::: :::WorkflowBlockItem Once the visit is approved following security and compliance checks, Sine activates the QR code credential in Siemens Sipass. ::: :::WorkflowBlockItem Sine delivers the QR code to the visitor via SMS or displays it on their printed badge. ::: :::WorkflowBlockItem The visitor presents the QR code at a reader with QR/barcode scanning support, and Siemens Sipass unlocks the door. ::: :::: **Check-out Flow:** ::::WorkflowBlock :::WorkflowBlockItem The visitor checks out via the Sine app, at a kiosk, by notifying their host, or automatically on exiting the geofence area. ::: :::WorkflowBlockItem Sine revokes the QR code credential in Siemens Sipass, preventing any further entry attempts using that credential. ::: :::: # Requirements ## Sine Requirements - **Integration enablement**: Suitable Sine subscription with the Sipass integration enabled (additional fees may apply) ## Siemens Sipass Requirements - **API License**: API license for remote credential provisioning - **Data adaptor**: Installation of the Sine data adaptor within Sipass. This is a middleware developed by Siemens that translates Sine's credential payloads into a compatible data format. - **QR Reader**: Compatible QR access readers (if using QR codes for access). This should be confirmed with Siemens or your Access Control Integration Partner, however something similar to [this](https://www.amazon.com/LBS-Outdoor-Control-Wiegand26-Scanner/dp/B08BRTD547) is suggested. - **Credential pool**: Available credential pool if using physical access cards - **Testing environment**: A sandbox environment or safe testing space - **Network connectivity**: Determine your method to connect Sine with your on-premise Sipass system. - **Direct API access**: Requires network firewall access to the Sipass API from outside your network # Configuration ## Siemens Sipass Configuration ### Sipass Configuration ::::WorkflowBlock :::WorkflowBlockItem **Enable API access** — Enable API access or open protocol support (REST API) in Sipass. ::: :::WorkflowBlockItem **API credentials** — Create API credentials or configure system access permissions for credential provisioning. ::: :::WorkflowBlockItem **Access zones** — Configure access zones and permission groups to control visitor access. ::: :::WorkflowBlockItem **Credential pool** — Verify that a credential pool or credential issuing capability is available. ::: :::WorkflowBlockItem **API documentation** — Prepare the API or protocol documentation required for the Sine integration setup. ::: :::: ## Sine Configuration ### General Setup ::::WorkflowBlock :::WorkflowBlockItem **Admin permissions** — Ensure you have `Team` or `Site Admin` permissions. These are required to configure integrations. ::: :::WorkflowBlockItem **Log in** — Log on to the Sine admin dashboard at [https://dashboard.sine.co](https://dashboard.sine.co). ::: :::WorkflowBlockItem **Select site** — Navigate to the `Locations` tab and click on the site you want to configure the integration for. ::: :::WorkflowBlockItem **Add integration** — In the Site menu, click on the `Integrations` menu item. Click the `Add integration` button and select `Siemens Sipass` from the list of available integrations. If the integration does not appear in the list, contact support. ::: :::WorkflowBlockItem **Name integration** — Enter a name for the integration. This can be anything, but choose a name that helps you identify what the integration is for. ::: :::: ### Connect to Siemens Sipass ### Connection Method - **Cloud to on-premise**: This integration establishes a direct connection from the Sine cloud to your on-premise system's API. ::::WorkflowBlock :::WorkflowBlockItem **Base URL** — Enter the URL and port for your Siemens Sipass server. For example, `https://your-siemens-sipass-server.com/api:1234`. ::: :::WorkflowBlockItem **Ignore SSL Certificate Check** — Turn this setting `ON` if you are using a self-signed certificate, as the Siemens Sipass integration will not be able to validate the certificate. ::: :::: ### Authentication ::::WorkflowBlock :::WorkflowBlockItem **API Key** — Enter your Siemens Sipass `API Key` and your `External ID`. The `External ID` can be any value. ::: :::WorkflowBlockItem **Test Connection** — Click the `Test connection` button to confirm that your configuration is correct. Once you have successfully verified that Sine can connect to your Siemens Sipass account, the `Integration Settings` section will become available. ::: :::: ### Integration Settings ### Credential Configuration This setting controls the type of access control credential generated when the integration runs. Select your preferred credential type below. ::::::Tabs :::::Tab{title="Sine QR Code"} Generates and attaches a QR code to a visitor's pass. The integration runs when a pass is created or expires, or when the visitor checks out. ::::WorkflowBlock :::WorkflowBlockItem **Send QR Code by SMS** — If the visitor's mobile number is available, send them a QR code credential to their phone. This can serve as a useful backup to a badge printer. ::: :::WorkflowBlockItem **Provision credential on check-in** — Select one or more visitor types for which you want the integration to provision credentials in your access control system when visitors check in using Sine. Ensure that the `Host Selection Required` checkbox is ticked for any visitor types used in access control integrations. Without this setting, visitors would receive access credentials without requiring host approval. You can review which of your visitor types have `Host Approval Required` enabled in the `General` tab of your site settings. ::: :::WorkflowBlockItem **Grace Period** — A visitor may check out using Sine before leaving the location but may still need their credentials to exit. You can set a grace period to ensure that access control credentials are not deprovisioned immediately after the visitor is checked out in Sine. ::: :::: ::::: :::Tab{title="Physical Assets"} Activates a physical asset (e.g., an HID card) in your Siemens Sipass system. The integration runs when an asset is assigned, returned, or marked as lost. - **Asset type** — Select the asset type applicable to this integration. You can create new asset types on the asset types page in the Sine Core Dashboard. ::Image[]{src="https://api.archbee.com/api/optimize/cIIINwBBlIs0Au1Y_bwqP/XcAEiQfIPF0cbUO-ifhhx_asset-types.png" size="75" position="flex-start" alt="asset-types" sha="9948c7af5630a38ed4cabebd9c506f0555d1785d" initialPath="/assets/integration-guide/siemens-sipass/asset-types.png" githubPath="docs/assets/integration-guide/siemens-sipass/asset-types.png" showCaption="false"} ::: :::::: ### Basic Configuration ::::WorkflowBlock :::WorkflowBlockItem **Connection details** — Enter the connection details specific to your access control system (API endpoint, credentials, IP address, or COM port). ::: :::WorkflowBlockItem **Field mapping** — Map Sine visitor fields to your access control system's cardholder schema. ::: :::WorkflowBlockItem **Test connection** — Test the connection and enable auto-provisioning for visitor check-in. ::: :::: ### Messages - **Visitor failure message** — Configure the message displayed to the visitor if the access control integration fails for any reason. ### Notifications - **Send integration failure notifications** — If the integration fails, you can enter one or more email addresses to be notified of the failure and its corresponding details. # Testing ::::WorkflowBlock :::WorkflowBlockItem **Create a test check-in** — Create a test visitor check-in using a visitor type configured for the integration. ::: :::WorkflowBlockItem **Verify credential provisioning** — Verify that the visitor profile is created in the vendor system and that credentials are provisioned correctly. ::: :::WorkflowBlockItem **Test credential access** — Test the credential at a compatible reader to ensure access is granted. ::: :::WorkflowBlockItem **Verify credential revocation** — Check out the test visitor and verify that access credentials are revoked after the configured grace period. ::: :::WorkflowBlockItem **Check failure notifications** — Monitor the integration failure notifications to ensure they are working correctly. ::: :::: *** *Need help? Contact Sine Support at* **[support@sine.co](mailto\:support@sine.co)**