Skip to content

API Overview

EMQX Cloud provides REST APIs for platform-level operations, broker deployment operations, and EMQX Fleets operations. Use this page to choose the right API type and understand the common access and authentication requirements.

API TypeScopeCredentialsReference
Platform APIManage platform-level resources, such as deployments, projects, TLS certificates, and audit logs.Platform API Key and SecretPlatform API
Broker Deployment APIManage broker deployment-level resources, such as clients, subscriptions, message publishing, and other deployment operations.Deployment App ID and App SecretBroker Deployment API
EMQX Fleets APIManage Fleets resources, such as thing types, things, device shadow, commands, jobs, and device credentials.Fleets deployment API Key and API SecretEMQX Fleets API

Access API Endpoints

Each API type has its own endpoint and credentials. See the corresponding API reference for how to obtain the endpoint. Access all APIs over HTTPS to ensure that data sent over the network is encrypted using TLS.

Authentication

HTTP APIs use Basic authentication. The username and password depend on the API type:

All secrets are displayed only once when they are created. Store them securely.

HTTP Status Codes

Common HTTP status codes for EMQX Cloud APIs include:

Status CodeDescription
200Success. The response body returns more information in JSON format.
400Invalid client request, such as an invalid request body or invalid parameters.
401Client authentication failed, possibly because the authentication credentials are invalid.
404The requested path cannot be found, or the requested object does not exist.
422Invalid properties.
500An internal error occurred while the server was processing the request.