Connect Larx to the systems your team already uses.
Satellite imagery providers, SCADA exports, GIS platforms, field operations tools, and custom data streams. Larx ingests, aligns, and enriches them all in one workspace.
Integration catalog.
Larx connects to the data sources your operations already depend on, with no custom middleware required for most connection types.
Satellite imagery providers
Commercial imagery providers with sub-daily revisit capability over your corridors. Larx handles scene ordering, cloud cover filtering, and baseline comparison automatically.
SCADA and sensor APIs
Connect SCADA historian exports and real-time sensor feeds via REST or MQTT. Larx aligns point sensor data to spatial coordinates and correlates readings with imagery events at the same location.
GIS and asset registries
Import corridor geometries and asset records from ArcGIS, QGIS, or any GeoJSON/Shapefile source. Larx uses your asset layer as the spatial reference for all detections and alerts.
Fixed camera streams
RTSP-compatible IP cameras at substations, pump stations, and access points stream directly into Larx. Zone-based alert rules apply to each camera feed independently.
Alert delivery channels
Alerts route to email, SMS, and webhook endpoints your team configures. Each channel supports filtering by asset type, severity level, and geography so the right crew gets the right alert.
Work order and field systems
Push confirmed alerts to Maximo, ServiceNow, or your work management system via webhook or REST export. Field crews get work orders pre-loaded with the spatial context from the triggering event.
REST API for custom data pipelines and internal tooling.
Every Larx workspace is API-accessible. Pull alert records, event timelines, and spatial context into your internal dashboards or custom reporting tools without building a separate pipeline.
Authentication uses standard bearer tokens. Rate limits are generous for operational use. Enterprise plans include dedicated API support and higher throughput for bulk historical queries.
Request API Access# Retrieve alerts from the past 7 days
curl -X GET "https://api.golarx.com/v1/alerts" \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-G \
-d "corridor_id=CORRIDOR-A7" \
-d "since=2026-09-15T00:00:00Z" \
-d "severity=high,critical"
# Response
{
"alerts": [
{
"id": "ALT-29410",
"type": "encroachment",
"severity": "high",
"corridor": "CORRIDOR-A7",
"coords": [-77.4318, 38.9271],
"detected_at": "2026-09-17T14:22:08Z",
"imagery_url": "https://..."
}
],
"total": 1
}Setup takes days, not quarters.
Most Larx integrations use existing connection types: file upload, REST API, or standard GeoJSON. There is no middleware layer to provision and no custom ETL to maintain. Onboarding connects what you already have to the Larx spatial processing layer.
For non-standard data formats or legacy SCADA historians, Larx's onboarding team works through data format normalization as part of the initial setup. Enterprise customers receive a dedicated implementation engineer for the first 30 days.
What happens when a data source goes offline.
Larx alerts your team when a connected data source stops sending readings, rather than silently dropping events. Sensor dropout is treated as a monitoring gap that needs acknowledgment, not a background error state.
Alert rules can be configured to escalate automatically if a source has been offline longer than a defined threshold. Your operations center always knows the confidence level of the current coverage picture.