Skip to main content
Connect Mirra to KODE OS for access control data integration

​
Overview

Use this integration to connect Mirra to KODE OS so you can synchronize access card and credential data with your C•CURE environment. REST and webhooks together keep cardholder and status information available in KODE OS for monitoring and downstream workflows.

​
Supported Capabilities

  • Collect Sensor Data
  • Receive Webhook Data

​
Prerequisites

  • An active account with Mirra and access to their API or developer portal
  • KODE OS environment with access to Data Sources

​
Configure Webhook

This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:
  1. Copy the webhook URL provided on the connector detail page
  2. In the Mirra platform, navigate to the webhook or notification settings
  3. Add a new webhook endpoint using the KODE OS URL
  4. Configure the authentication header as specified on the connector detail page
  5. Save and enable the webhook

​
Configure Connector in KODE OS

  1. Navigate to Data Sources in your building
  2. Click API Catalog and search for Mirra
  3. Click + Add Datasource
  4. Fill in the fields below and complete the three-page setup flow

​
What Data You Get

​
Access Cards

Access card and credential records including cardholder information and card status

​
Polling Schedule

  • AccessCard
For more details on collection modes, see the Data Collection guide.

​
Use Cases

Once connected, this integration enables you to:
  • Centralize access event monitoring across all entry points and zones
  • Generate audit trails for security compliance and investigation
  • Correlate access patterns with occupancy and energy data for building optimization

​
Troubleshooting

Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Double-check all credential fields match the values from the Mirra platform.
Verify the webhook URL is correctly registered in the Mirra platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the Mirra system can reach the KODE OS webhook endpoint over the network.
Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Mirra API.
Last modified on March 29, 2026