Beta API for creating a cloud site from a partner application, including validation, device scanning and retry limitations.
In beta and available on request. This implementation is not part of the standard release. Software review and controller-level validation of the latest changes are still pending. Contact Eniris through your existing support channel to confirm availability and arrange validation before using it on a live portfolio.
The onboarding API creates one site per request on a Cloud controller controller. It validates the site identifier, address, supported cloud connections and optional data sources, scans for devices and saves the site's configuration. It does not enable cloud support for a device that is not supported already.
POST /api/sites/create/ accepts a JSON object. When a proxy forwards requests as form data, the same object can be JSON-encoded in the payload form field. The request contains siteId, address and devices; datasources is optional. Eniris provides the connection-specific fields for the selected integration.
Use the approved authenticated access route for your cloud controller. Invalid or unsupported requests are rejected before device scanning. This endpoint is for cloud controllers and single-site cloud connections; integrations requiring an interactive authorization step must complete their supported onboarding flow separately.
Adding ?dry-run performs validation and a real device scan, without saving the site. A scan can consume a single-use authorization code or rotate a refresh token, for example with SolisCloud. Obtain fresh credentials before the real create after such a dry-run. The same applies when a create fails after scanning: rolling back local site configuration cannot undo an external token exchange.
A successful dry-run is not evidence that live monitoring or control has been commissioned.
Site operations share the controller's I/O service. Scans require that service to reload; successful creates also restart the data logger and scheduler. Schedule onboarding with Eniris when these interruptions affect existing sites. This is not an uninterrupted bulk-import interface.
Send one operation at a time. HTTP 409 means another site operation is still in progress; wait before retrying. After a timeout, check whether the site already exists before submitting it again. If a failed operation reports incomplete cleanup, resolve the remaining site configuration before retrying, and renew any credentials consumed by the scan.
Before extending onboarding to a portfolio, validate one site: its device identities, measurements, data-source configuration and normal operation after the service reload. Control tests require a separately agreed commissioning procedure.