CONPDS TRACKER

Integration Guide — Output Formats & Integration Paths

Tracker publishes container numbers as open JSON via MQTT. This guide covers the output format, integration methods, the Open Platform vs Autogate decision, and how to build custom workflows on Tracker's data layer.

Open JSON · MQTT · REST API · Direct database · Any DMS / TOS / WMS

Open JSON Output via MQTT

Every confirmed container number read is published as a structured JSON message to the MQTT broker. Each message includes the container number, camera ID, camera group, timestamp, and confidence score. Results are published per camera or per camera group — any MQTT subscriber receives the data instantly.

No proprietary format, no vendor lock-in. Any system that can subscribe to an MQTT topic can consume Tracker's output — a depot management system, terminal operating system, warehouse management system, a custom webhook, or a direct database write.

Every read published as structured JSON to the MQTT broker — no proprietary format, no vendor lock-in

Any MQTT subscriber receives the data instantly: your DMS, TOS, WMS, a custom webhook, or a direct database write

Integration via MQTT, REST APIs, or direct database integration — standard protocols, no middleware required

ConPDS provides custom integration support for non-standard environments on request

Three Integration Paths — Standard Protocols, No Middleware

Path 01 · Primary

MQTT Subscription

Subscribe to MQTT topics per camera or camera group

JSON messages delivered in real time — as low as 30ms from capture

Any MQTT client library in any programming language

Ideal for real-time gate automation, alert systems, and event-driven workflows

Path 02 · API

REST API Integration

Query OCR results via REST endpoints

Standard HTTP/JSON — integrates with any web service

Authentication via Certificate, API key, Basic Auth, or URL Auth

Ideal for polling-based integrations and dashboard systems

Path 03 · Database

Direct Database Integration

Write OCR results directly to your SQL or NoSQL database

No middleware layer required — Tracker writes to your schema

Suitable for facilities with existing database-driven workflows

On-Premise Infrastructure — Any Camera, Any Facility Size

Runs on your hardware — Windows 10+ / Linux Ubuntu 20+ — nothing leaves your network

Connects simultaneously to multiple concurrent IP camera RTSP streams — 5 at a small depot, 50 across a large terminal, same software throughout

Streams organised into camera groups — a group can represent a gate lane, a yard zone, a crane position, or any logical unit the facility defines

GPU-accelerated processing — Nvidia CUDA or Intel HD; processing capacity scales with hardware as camera count grows

Centralised OCR engine — update Tracker once and every connected camera stream benefits immediately, with no manual firmware upload or per-camera reconfiguration required

For full hardware and camera specifications, see the Tracker Technical Specifications.

What Do You Want to Build on Tracker's OCR Output?

Tracker publishes container numbers as open JSON via MQTT — what happens next is your choice. Two paths are available.

Open Platform · Any DMS · Any Workflow

Build Your Own Integration

Tracker's MQTT output is your data layer. Subscribe any system to the feed — your DMS, TOS, WMS, a custom webhook, or a direct database write. No ConPDS middleware required. Integration is available via MQTT, REST APIs, or direct database integration.

Any MQTT Subscriber JSON published per camera or camera group — consumed by DMS, TOS, WMS, REST APIs, SQL databases, or any custom application.

No Management System Dependency Works independently of any DMS, TOS, or WMS — DepotMaster, EOS, AEMS, or systems you've built yourself. Integrate with whatever you run, or with nothing at all.

Custom Integration & Workflow Development Tracker's job ends at the MQTT publish — what happens next is business logic built on top of that data. ConPDS's team can help design and build custom integrations, routing rules, and automated workflows as a separate engagement.

Pre-Built Solution · DepotMaster Depots Only

ConPDS Autogate — Ready to Deploy

ConPDS Autogate is the complete gate automation solution built on Tracker. It adds the physical installation and the DepotMaster integration layer — cameras, kiosk totem with QR scanner, safety-interlocked barrier, video intercom, and full reservation matching logic. Tracker's OCR output becomes barrier decisions and self-service driver interaction, without a gate officer present.

Requires DepotMaster. Autogate is designed specifically for depots running DepotMaster as their DMS. If your operation uses a different DMS, the open platform path on the left is your starting point.

Complete Physical Installation Cameras, kiosk totem, QR scanner, safety-interlocked barrier with lane sensors, video intercom, network equipment — one integrated system.

Observed at Live Deployments Gate events that previously took several minutes now complete in seconds — from truck approaching cameras to barrier opening, no manual involvement.

See ConPDS Autogate →

Ready to Integrate ConPDS Tracker?

Tell us about your current systems, integration requirements, and what you want to build on Tracker's OCR output — we will provide a tailored integration plan and answer technical questions within one business day.

Read the technical specifications →

No obligations — reply within 1 business day

Integration Guide — Output Formats & Integration Paths

Open JSON Output via MQTT

Three Integration Paths — Standard Protocols, No Middleware

MQTT Subscription

REST API Integration

Direct Database Integration

On-Premise Infrastructure — Any Camera, Any Facility Size

What Do You Want to Build on Tracker's OCR Output?

Build Your Own Integration

ConPDS Autogate — Ready to Deploy

Ready to Integrate ConPDS Tracker?

Related Resources

ConPDS Tracker

Tracker Technical Specifications

ConPDS Autogate

Autogate System Architecture

What Is Container Operational Evidence?