The API server acts as the central communication hub, exposing secure endpoints that allow both users and agents to interact with the Red Hat Edge Manager service.

The API server exposes the following endpoints:

User-facing API endpoint

Users can connect to the user-facing API endpoint from the command-line interface (CLI) or the web console. Users must authenticate with the configured external authentication service to obtain a JSON Web Token (JWT) to make HTTPS requests.

On standalone Red Hat Enterprise Linux deployments, users reach the user-facing API through the HTTPS gateway on port 443 at path prefixes /\_/flightctl/ and /api/v1/. The gateway also accepts flightctl login https://<baseDomain> without a path suffix. Port 3443 is not required for new installations; the gateway can continue to expose it after upgrade for clients that still target that port. For routing and TLS details, see HTTPS gateway for standalone Red Hat Enterprise Linux deployments in the Additional resources section.

Agent-facing API endpoint

Agents connect to the agent-facing endpoint, which is mutual TLS (mTLS)-protected. On standalone Red Hat Enterprise Linux, the gateway forwards TCP port 7443 to the agent listener without terminating TLS. The service authenticates devices by using X.509 client certificates.

The Red Hat Edge Manager service also communicates with various external systems to authenticate and authorize users, get mTLS certificates signed, or query configuration for managed devices.