Deprecations

Deprecated endpoints are listed here and marked deprecated in the API Explorer. Deprecated functionality continues to work but will be removed in a future version — migrate to the recommended replacement.

Endpoints

Endpoint	Status	Replacement
POST /api/v1/account	Deprecated	Use POST /api/v3/account with type: SINGLE or type: FAMILY. The v3 endpoint unifies single, family, and business creation in one call.
POST /api/v1/account/business	Deprecated	Use POST /api/v3/account with type: BUSINESS.
GET /api/v1/alarms/{alarmId}/close	Deprecated	Closing an alarm mutates state (status -> CLOSED); it should use a POST. Avoid relying on GET for this.
GET /api/v1/account/{id}/alarms/{alarmId}/close	Deprecated	Same as above, on the CRM surface.

How deprecations are signaled

• In the spec: deprecated operations carry deprecated: true and an x-deprecated-replacement note in the OpenAPI document.
• In the Explorer: deprecated operations are visibly flagged.
• Here: this page is the human-readable registry of what to migrate.