Development Specification

Device message callbacks: Receive device messages · Push configuration.

Device control and events (v2): Capability usage · Capabilities overview.

Request body, signature, and the worked sign example have moved to Public conventions. Technical values there are the same as this page used to carry.

1. Interface domain name description

Imou Cloud OpenPlatform provides access domain names in multiple regions. Please select the access domain name address based on the data center to which the developer's account belongs, in order to obtain the best platform service experience. The data center to which the developer belongs can be viewed in "Control Board - Basic Information - My Information".

Host pattern: https://openapi-[DataCenter].easy4ip.com.

Replace {method} with the method name on each API page. Port :443 is optional.

2. Short call checklist

1. Copy AppId / AppSecret from Console → My Apps → App Info.
2. Build the JSON request body and check time / nonce: Request conventions.
3. Calculate system.sign on the server: Signature.
4. Call accessToken. Valid for 3 days; refresh on TK1002.
5. Read result.code in Return codes. Daily limits: Interface call limits.
6. First walkthrough: First API call.

3. Error codes on each API page

Match the domestic book: under #### Error codes, compose **`

include 未找到：en/devcap/errors/….md

** fragments (gateway, sub-account, device bind, cloud storage, DV20xx, etc.). Fragments live under .vuepress/fragments/` and stay in sync with Return codes.

• Typical OpenAPI page: gateway plus 0–2 context fragments such as sub-account, dv10-device-base, dv10-bind, or st-cloud.
• Capability property/set/invoke leaves: gateway + dv20-property-set or dv20-invoke (see domain examples).
• Return codes is the full HTTP index; Capability errors lists all DV20xx.

Link-only error sections (no includes) are not allowed.