Integration Guide — Connecting BetaTrac Platforms with Your Existing Systems

Content Type: Integration Guide Audience: IT Administrators, Operations Managers, System Integrators Estimated Read Time: 12 minutes

---

Purpose

This guide explains how BetaTrac's three platforms integrate with external systems your organisation may already operate — HR databases, access control systems, payroll platforms, CCTV networks, and government compliance portals. Understanding these integration points helps you plan deployment without disrupting existing workflows.

BetaTrac's products are distributed across three independent platforms. Each platform exposes its own set of integration endpoints. This guide is organised by platform so you can identify which integrations apply to your specific product subscriptions.

---

Integration Principles

Before reviewing specific endpoints, it is important to understand the following principles that apply to all three platforms:

1. API-First Architecture — Every platform exposes a RESTful API. No integration requires direct database access or file-level manipulation.

2. Read and Write Separation — Integrations can be configured as read-only (the platform pulls data from your system) or write-enabled (the platform pushes data to your system). Most integrations support both directions.

3. No Shared Database — The three platforms do not share a database. If you integrate an external system with one platform, data from the other two platforms is not automatically available to that integration. Each platform maintains its own API surface.

4. Webhook Support — All platforms support outbound webhooks for event notifications. Webhooks can be configured per event type (incident created, patrol completed, vehicle geofence breach, evidence uploaded, etc.) and delivered to any HTTPS endpoint.

5. Credential Management — API keys and webhook secrets are managed per platform. A credential for Platform 1 does not grant access to Platform 2 or Platform 3.

---

Platform 1 — Guarding Suite Integrations

Products: eGuard, eGuard-K9, ePatrol, ePatrol-Pro, eSmartPatrol, ePatrol-Mobile

HR System Synchronisation

Supported direction: Bidirectional (read from HR, write back to the Guarding Suite)

The Guarding Suite can synchronise guard personnel data with your existing HR or payroll system. This integration eliminates the need for manual roster management when staff join, transfer, or leave.

• Data synchronised: Employee ID, full name, contact number, email, employment status, site assignment, shift schedule.
• Sync frequency: Configurable — real-time (on HR record change), hourly, or daily batch.
• Supported HR systems: Any system that exposes a REST API or supports CSV/SFTP file export. Common configurations include BambooHR, SAP SuccessFactors, Oracle HCM, and custom in-house databases.
• Conflict resolution: When a platform record and an HR record disagree, the HR system is treated as the source of truth for personnel data. Platform-specific fields (e.g., patrol assignment, incident history) are preserved.

Access Control System Integration

Supported direction: Read from access control, write events to the Guarding Suite

If your site uses an existing physical access control system (e.g., HID, Cognito, Lenels, bio-vision), the Guarding Suite can ingest access events and correlate them with patrol activity.

• Events ingested: Door open, door denied, badge presented, alarm trigger.
• Correlation: Access events are displayed on the patrol live view alongside checkpoint scans, allowing operators to see both guard activity and access system activity in a single timeline.
• Alert rules: You can configure rules that trigger alerts when specific access events occur without a corresponding patrol check-in (e.g., a door opens but no guard is on site).

Payroll Export

Supported direction: Write from the Guarding Suite to payroll system

The Guarding Suite can export shift, patrol, and overtime data in formats compatible with standard payroll systems.

• Export formats: CSV, JSON, and direct API push.
• Data included: Employee ID, shift start and end times, total patrols completed, overtime hours, incident count.
• Scheduling: Exports can be scheduled weekly, fortnightly, or monthly to align with your payroll cycle.

---

Platform 2 — Vehicle & Evidence Integrations

Products: RapidTrac Compact, DashCams

Fleet Management System Integration

Supported direction: Bidirectional

RapidTrac Compact integrates with existing fleet management and telematics systems to provide a unified vehicle tracking view or to supplement an existing fleet platform.

• Data exchanged: Vehicle GPS position, speed, heading, driver assignment, geofence events.
• Supported protocols: REST API, MQTT for real-time position streaming, and legacy CSV/SFTP for older systems.

Platform 3 — Data & Communications Integrations

Products: Data-Armour, RADR, eTrac, eTrac-IS, RFID-Asset-Management, e-100, e-200

• Integration method: Data-Armour presents an S3-compatible endpoint. Your existing backup software writes to this endpoint as it would any S3 bucket. Data-Armour handles versioning, immutability, and ransomware isolation automatically.
• No agent installation: Data-Armour does not require an agent to be installed on your backup source. The integration is entirely via standard S3 protocol.

RFID Reader Integration

Supported direction: Read from RFID readers, write events to RFID-Asset-Management

The RFID Asset Management module integrates with physical RFID readers deployed at your sites.

• Supported reader types: NordicID and Brady scanners.
• Integration method: The RFID Asset Management service connects directly to each reader via LLRP over TCP. No middleware is required.
• Event data: Each read event includes the tag EPC, reader ID, antenna ID, RSSI (signal strength), and timestamp. The service deduplicates consecutive reads of the same tag within a configurable window (default: 5 seconds).

Government Compliance Reporting

Supported direction: Write from the platform to compliance portal

For government and public sector deployments, the platforms can generate compliance reports in formats accepted by South African regulatory portals.

• Report types: Incident summaries, patrol completion records, access event logs, vehicle fleet compliance certificates.
• Delivery methods: Secure API upload to the compliance portal, or scheduled report generation with manual download and submission.
• Data retention: Reports are retained within the platform for a configurable period (default: as per client request) to support regulatory audit requirements.

---

Webhook Configuration

All three platforms support outbound webhooks. This is the most common integration pattern for organisations that want to receive real-time event notifications in their own systems (e.g., a Security Information and Event Management (SIEM) platform, a custom dashboard, or a notification service).

Configuring a Webhook

1. Navigate to the platform's web interface → Settings → Integrations → Webhooks.
2. Click Add Webhook.
3. Enter the following details:
   • Name: A descriptive name for the webhook.
   • Destination URL: The HTTPS endpoint on your system that will receive the webhook.
   • Event Types: Select which events trigger the webhook (e.g., incident created, patrol completed, vehicle geofence breach, evidence uploaded).
   • Secret: A shared secret used to sign each webhook payload. Your receiving system must validate this signature to confirm the webhook originated from the platform.
4. Save the webhook configuration.
5. Use the Test button to send a sample payload to your endpoint and verify connectivity.

Webhook Payload Format

All webhooks deliver a JSON payload with the following structure:

• event_type: The event category (e.g., incident.created, patrol.completed, vehicle.geofence_breach).
• event_id: A unique identifier for this webhook delivery.
• timestamp: ISO 8601 timestamp of when the event was generated.
• platform: The platform that generated the event (1, 2, or 3).
• data: The event-specific payload containing relevant record data.

Retry Policy

If your endpoint does not respond with a 2xx HTTP status code within 10 seconds, the platform will retry delivery with exponential backoff: 1 minute, 5 minutes, 30 minutes, 2 hours, and 8 hours. After 5 failed attempts, the webhook is marked as failed and the platform admin receives a notification. No webhooks are silently dropped.

---

Pre-Integration Checklist

Before beginning any integration, confirm the following:

• [ ] You have identified which platform(s) the integration applies to.
• [ ] You have administrative access to both the platform and the external system.
• [ ] You have documented the data fields that need to be exchanged and their direction (read vs. write).
• [ ] Your receiving system can accept webhooks over HTTPS with a valid TLS certificate.
• [ ] You have a test environment for the external system where you can validate the integration before going live.
• [ ] You have a rollback plan in case the integration needs to be disabled.

---

Support During Integration

If you encounter issues during integration, contact BetaTrac support with the following information:

• The platform name (Platform 1, 2, or 3) and the specific product.
• The external system name and version.
• A description of the issue, including any error messages.
• The approximate time the issue occurred.

BetaTrac support can assist with configuration, but does not modify the external system. If the external system requires changes, those must be coordinated with your system's vendor or internal IT team.