Quanergy

QORTEX DTC API

The QORTEX DTC API is the integration surface of Quanergy's detect-track-classify perception server. A gRPC service on port 17177 (Protocol Buffers 3) covers zone, counter-line, rule, PTZ camera, settings, recording, playback, state and file-streaming operations, gated by a stateful SwitchToConfigMode stream. Alongside it, configurable TCP publishers fan out the trackable list, zone list, counter-line counts, point cloud and sensor-health state, and a small HTTP command server on port 8080 handles HTTP Digest authentication and AES-256 key issue. The server is customer-hosted on Ubuntu, Windows, a VM or Docker; there is no Quanergy-operated endpoint.

GitHub

Documentation

📖
APIReference
https://downloads.quanergy.com/qortex/Qortex-API-Reference-RevA-120824.pdf
📖
Documentation
https://downloads.quanergy.com/qortex/Qortex-UserGuide-RevP-120824.pdf
📖
GettingStarted
https://downloads.quanergy.com/qortex/QPN-96-00131-Quick%20Start%20Card%20%E2%80%93%20Q-Track%20-%20Rev%20A.pdf
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/quanergy/refs/heads/main/authentication/quanergy-authentication.yml

Other Resources

🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/quanergy/refs/heads/main/conventions/quanergy-conventions.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/quanergy/refs/heads/main/errors/quanergy-problem-types.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/quanergy/refs/heads/main/data-model/quanergy-data-model.yml
🔗
EventCatalog
https://raw.githubusercontent.com/api-evangelist/quanergy/refs/heads/main/asyncapi/quanergy-qortex-dtc-events.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/quanergy/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
name: QORTEX DTC API
description: The QORTEX DTC API is the integration surface of Quanergy's detect-track-classify perception
  server. A gRPC service on port 17177 (Protocol Buffers 3) covers zone, counter-line, rule, PTZ camera,
  settings, recording, playback, state and file-streaming operations, gated by a stateful SwitchToConfigMode
  stream. Alongside it, configurable TCP publishers fan out the trackable list, zone list, counter-line
  counts, point cloud and sensor-health state, and a small HTTP command server on port 8080 handles HTTP
  Digest authentication and AES-256 key issue. The server is customer-hosted on Ubuntu, Windows, a VM
  or Docker; there is no Quanergy-operated endpoint.
humanURL: https://quanergy.com/products/q-track/
baseURL: https://<IP_Address>:8080/v1
x-deployment: on-premises
x-baseurl-note: Quanergy operates no hosted endpoint. The value above is the URL form published verbatim
  on page 92 of the QORTEX DTC for Q-Track API Reference; the host is the customer's own QORTEX DTC server.
  The gRPC surface is reached at <IP_Address>:17177.
x-transports:
- protocol: grpc
  port: 17177
- protocol: http
  port: 8080
  base_path: /v1
- protocol: tcp
  ports:
  - 17161
  - 17163
  - 17168
  - 17172
  - 17173
  - 17175
  - 17176
  - 17178
tags:
- LiDAR
- Perception
- Physical Security
- gRPC
- Streaming
properties:
- type: APIReference
  url: https://downloads.quanergy.com/qortex/Qortex-API-Reference-RevA-120824.pdf
- type: Documentation
  url: https://downloads.quanergy.com/qortex/Qortex-UserGuide-RevP-120824.pdf
- type: GettingStarted
  url: https://downloads.quanergy.com/qortex/QPN-96-00131-Quick%20Start%20Card%20%E2%80%93%20Q-Track%20-%20Rev%20A.pdf
- type: Authentication
  url: authentication/quanergy-authentication.yml
- type: Conventions
  url: conventions/quanergy-conventions.yml
- type: ErrorCatalog
  url: errors/quanergy-problem-types.yml
- type: DataModel
  url: data-model/quanergy-data-model.yml
- type: EventCatalog
  url: asyncapi/quanergy-qortex-dtc-events.yml