Imou Open Platform Production Checklist: Devices, Events, Permissions and Storage

Before production, prove one complete lifecycle with the actual account region, devices, firmware, services, and client: signed backend access, supported onboarding and binding, device/channel inventory, least-privilege authorization, callback HTTP 200 and downstream processing, optional media behavior, storage queries, live-address controls, credential protection, observability, offboarding, and recovery. Documentation establishes interfaces; your pilot must establish that the selected combination works.

Why it matters

Most integration demos prove only a happy-path frame or successful API response. Production failures happen between those moments: a device generation needs an SDK-assisted binding path, a callback route returns a redirect, an event has no image, a sub-account lacks channel permission, or a live address is paused. A production gate should test transitions and boundaries, not simply count completed endpoints.

The Imou homepage groups the platform into device access, video security, value-added services, app development, Home Assistant, and SaaS-oriented management. Use that map to identify dependencies, then use live method documentation and deployment evidence for approval.

Approach / architecture

Assign an owner and proof artifact to each plane:

Plane	Production proof	Owner
Credentials and region	Console assignment, signed test, secret controls	Platform/backend
Device onboarding	Supported state transitions on target versions	Mobile/device/backend
Inventory	Device/channel/capability reconciliation	Backend
Authorization	Allowed and denied user/resource tests	Security/backend
Events	Public callback, exact 200, durable processing	Backend/operations
Evidence and storage	Snapshot/video query and missing-media UX	Product/backend
Live operations	Address, plan, and status runbook	Operations
Client	Verified mobile, PC, browser, or HA workflow	Client team
Lifecycle	Credential rotation, device removal, user offboarding	Security/operations

Keep AppSecret, administrator tokens, signing, and administrative OpenAPI calls in a trusted backend. Place only documented client responsibilities in OpenSDK or web components. Your product owns tenant authorization even when Imou sub-account permissions are also used.

Seven production gates

1. Prove application identity and regional routing. Record the data center assigned in Control Board and map the credential set to the documented SG, FK, or OR endpoint. Run the official signing test and a real signed request. Reject unknown region config at startup.

2. Prove onboarding for supported combinations. Test network configuration, initialization, binding, resume after interruption, existing binding, and device removal with the device and software versions you will support. Follow current OpenSDK demos where SDK-assisted binding is required.

3. Prove inventory and capability decisions. Reconcile every bound device and channel into your product model. Drive controls from returned capabilities and services, not a universal model promise. Test offline and unsupported states.

4. Prove least privilege. Classify every method by administrator versus sub-account token. Test the minimum documented resource and permission, wrong tenant, wrong channel, removed policy, and attempts to invoke administrator work through user routes.

5. Prove callback recovery. Verify the public URL, TLS, exact HTTP 200, durable enqueue, family-specific parsing, duplicate handling, and downstream failure isolation. Test saved callback configuration and a re-subscription runbook without inventing retry counts.

6. Prove evidence, storage, and live behavior. Render events without images, process images only where present, test snapshot and video queries where subscribed, and operate live addresses using exact address-, stream-, and plan-state fields. Do not assume entitlement or media completeness.

7. Prove operations and offboarding. Build redacted diagnostics, alert ownership, controlled config changes, user removal, device unbinding, live-address cleanup, credential rotation, and rollback. Run an incident exercise before scaling.

APIs / SDKs

Start at the Imou Open Platform homepage for the product map. Use the following current sources as implementation boundaries:

• HTTP development specification for regional endpoints, request envelope, and signatures;
• mobile application guide for SDK/backend responsibility and version-dependent binding;
• account docking for sub-accounts and policies;
• event push process and event formats;
• getCloudRecords for snapshot/video record queries;
• live module for address and plan lifecycle; and
• the verified PC guide and docking-mode comparison when evaluating desktop.

Method pages win over summaries. Save the source and review date in each production control.

Required test evidence

For each gate, retain environment, application reference, account region, device and software version, SDK/client version, method, sanitized request ID and result, expected outcome, observed outcome, and reviewer. Never include AppSecret, full access tokens, device passwords, verification codes, signed media URLs, reusable live addresses, or unredacted customer payloads.

Evidence should distinguish documented fact from application policy. For example, HTTP 200 is a documented callback requirement; your queue, timeout, retry, deduplication, and alert thresholds are internal design. liveStatus values are documented; your incident severity and remediation are internal policy.

Release and rollback

Release first to a small, known inventory. Confirm onboarding, one permitted user flow, one denied flow, one callback event, one media-absent event, one storage query where applicable, and one controlled live-state observation. Expand only after logs and support tools can explain each stage.

Rollback must preserve authorization and evidence. Define how to disable a client feature without exposing broader credentials, restore callback routing, revert endpoint config, and reconcile any device, policy, or live-address writes made during deployment.

Limits & pitfalls

• Do not approve production from one successful live frame.
• Do not promise all models, firmware, events, images, storage, playback, talk, PTZ, or client features.
• Do not expose AppSecret, administrator tokens, sub-account tokens, signed images, or live addresses.
• Do not select regional endpoints from end-user geography or infer data residency from hostname labels.
• Do not invent callback retry counts, platform latency, implementation duration, or SLA.
• Do not publish prices, storage unit costs, entitlement quantities, or universal retention from technical pages.
• Do not invent AI endpoints or promise AI results.
• Do not use administrator authority as a fallback for failed user-scoped calls.
• Do not use guessed /book/en/pc/ paths; the verified PC guide is /book/pc/summary.html.
• Recheck live documentation on release and publication day.

Go/no-go record

The final record should name unresolved risks. “Not tested” is a no-go for a required journey, but it can be an explicit non-feature for out-of-scope capabilities. Document supported combinations narrowly, give users honest unavailable states, and create a revalidation trigger for SDK, device software, account region, service, endpoint, or callback changes.

Use Imou Open Platform to assemble a one-device production rehearsal, and promote only after every required lifecycle gate has current, sanitized evidence.