Shelly-NG supports a minimal subset of HTTP endpoints used specifically for device control. The reason for including the HTTP compatibility layer in Shelly-NG is to give our clients smooth transition path from the Classic Shelly devices to Gen2 by providing the ability to control the new devices through a familiar mechanism, namely the Classic Shelly API.
All shellies from both Gen1 and Gen2 families expose the
/shelly endpoint, useful for discovery of devices and their features and capabilities.
Functional components also expose their own set of compatibility HTTP resources, documented on their respective pages, for example