These APIs are not exposed to end users. They serve internal infrastructure, deployment automation, and third-party service integration.
Purpose: Provides connection details (hostname, port, database name, credentials) for DB roles assigned to services on a given host.
Primary consumer: Third-party services (backup tools, reporting pipelines, Telegraf) that need direct PostgreSQL access to instance databases.
Location: Runs on each host as part of iot-api.
Security: Restricted by deployment configuration. Only accessible from trusted infrastructure.
This is the recommended API for external service integration.
Purpose: DBM-to-host orchestration — node registration, catalog sync, control operations.
Location: Exposed by DBM.
Security: Must never be accessible from outside. Restrict to trusted infrastructure with mTLS/TLS.
Purpose: Exposes local routing information for services on a host.
Location: Runs on each host as part of iot-node-manager.
Consumer: IoT Nginx Updater (to build per-host Nginx routing fragments).
Purpose: Exposes global routing table from DBM for all hosts and instances.
Consumer: IoT Nginx Updater.
See Gateway API for details.
Use JSON-RPC API instead.