Start with the application and account region, provision and bind one device, inventory its device/channel resources, then add callbacks, least-privilege permissions, storage, and the appropriate client surface. Keep credentials and OpenAPI operations on a trusted backend. This roadmap links each task to a planned canonical article and current official documentation; relative links are drafts, not claims that those pages are already published.
How to use this roadmap
Imou Open Platform spans device access, video security, value-added services, application development, Home Assistant, and SaaS-oriented integration. The useful question is not whether every project needs every surface. It is which responsibility comes next, which source is authoritative, and where secrets and end-user authorization belong. Use this page as a routing map rather than a substitute for interface reference.
Responsibility architecture
| Layer | Responsibility | Boundary |
|---|---|---|
| Device/client | Provisioning, device initialization, media UX | Capability varies by device and SDK |
| Trusted backend | Credentials, OpenAPI, authorization, callback receiver | Never expose App Secret or administrator token |
| Imou Open Platform | Documented cloud APIs, SDKs, messages, services | Current docs define methods and fields |
| Product/Home Assistant | User experience and automations | Must remain capability- and quota-aware |
Task map: planned canonical articles 01–29
01. Platform Scope And Build Choices
Planned canonical: platform scope and build choices — Covers platform scope and build choices. This relative path marks an unpublished batch article; replace it only after a real URL exists.
02. Smartconfig, Softap, Or Wired Provisioning
Planned canonical: SmartConfig, SoftAP, or wired provisioning — Covers SmartConfig, SoftAP, or wired provisioning. This relative path marks an unpublished batch article; replace it only after a real URL exists.
03. Binding Behavior On Security-Upgraded Devices
Planned canonical: binding behavior on security-upgraded devices — Covers binding behavior on security-upgraded devices. This relative path marks an unpublished batch article; replace it only after a real URL exists.
04. Device And Channel Resource Model
Planned canonical: device and channel resource model — Covers device and channel resource model. This relative path marks an unpublished batch article; replace it only after a real URL exists.
05. Paginated Fleet Inventory
Planned canonical: paginated fleet inventory — Covers paginated fleet inventory. This relative path marks an unpublished batch article; replace it only after a real URL exists.
06. Device-Business Access Routes
Planned canonical: device-business access routes — Covers device-business access routes. This relative path marks an unpublished batch article; replace it only after a real URL exists.
07. Callback Subscription Settings
Planned canonical: callback subscription settings — Covers callback subscription settings. This relative path marks an unpublished batch article; replace it only after a real URL exists.
08. Event Payloads And Image Availability
Planned canonical: event payloads and image availability — Covers event payloads and image availability. This relative path marks an unpublished batch article; replace it only after a real URL exists.
09. Callback Delivery Stopping
Planned canonical: callback delivery stopping — Covers callback delivery stopping. This relative path marks an unpublished batch article; replace it only after a real URL exists.
10. Alarm-Image Decryption Boundary
Planned canonical: alarm-image decryption boundary — Covers alarm-image decryption boundary. This relative path marks an unpublished batch article; replace it only after a real URL exists.
11. Callback And Query Reconciliation
Planned canonical: callback and query reconciliation — Covers callback and query reconciliation. This relative path marks an unpublished batch article; replace it only after a real URL exists.
12. Administrator And Sub-Account Tokens
Planned canonical: administrator and sub-account tokens — Covers administrator and sub-account tokens. This relative path marks an unpublished batch article; replace it only after a real URL exists.
13. Least-Privilege Camera Permissions
Planned canonical: least-privilege camera permissions — Covers least-privilege camera permissions. This relative path marks an unpublished batch article; replace it only after a real URL exists.
14. Permission Inheritance And Addpolicy Limits
Planned canonical: permission inheritance and addPolicy limits — Covers permission inheritance and addPolicy limits. This relative path marks an unpublished batch article; replace it only after a real URL exists.
15. Application Users And Sub-Accounts
Planned canonical: application users and sub-accounts — Covers application users and sub-accounts. This relative path marks an unpublished batch article; replace it only after a real URL exists.
16. Snapshot Versus Video Storage
Planned canonical: snapshot versus video storage — Covers snapshot versus video storage. This relative path marks an unpublished batch article; replace it only after a real URL exists.
17. Cloud-Storage Activation
Planned canonical: cloud-storage activation — Covers cloud-storage activation. This relative path marks an unpublished batch article; replace it only after a real URL exists.
18. Cloud-Record Enumeration
Planned canonical: cloud-record enumeration — Covers cloud-record enumeration. This relative path marks an unpublished batch article; replace it only after a real URL exists.
19. Homepage-Level Ai Insight Scope
Planned canonical: homepage-level AI Insight scope — Covers homepage-level AI Insight scope. This relative path marks an unpublished batch article; replace it only after a real URL exists.
20. Opensdk And Backend Responsibility
Planned canonical: OpenSDK and backend responsibility — Covers OpenSDK and backend responsibility. This relative path marks an unpublished batch article; replace it only after a real URL exists.
21. Mobile Talk And Download
Planned canonical: mobile talk and download — Covers mobile talk and download. This relative path marks an unpublished batch article; replace it only after a real URL exists.
22. Pc Opensdk Versus Web
Planned canonical: PC OpenSDK versus web — Covers PC OpenSDK versus web. This relative path marks an unpublished batch article; replace it only after a real URL exists.
23. Web Or H5 Without Native Development
Planned canonical: web or H5 without native development — Covers web or H5 without native development. This relative path marks an unpublished batch article; replace it only after a real URL exists.
24. Hls, Rtmp, And Live-Address Control
Planned canonical: HLS, RTMP, and live-address control — Covers HLS, RTMP, and live-address control. This relative path marks an unpublished batch article; replace it only after a real URL exists.
25. Live-Address Audit And Scheduling
Planned canonical: live-address audit and scheduling — Covers live-address audit and scheduling. This relative path marks an unpublished batch article; replace it only after a real URL exists.
26. Core Integration Versus Maintained Component
Planned canonical: Core integration versus maintained component — Covers Core integration versus maintained component. This relative path marks an unpublished batch article; replace it only after a real URL exists.
27. Push Alarms Beside Polling
Planned canonical: push alarms beside polling — Covers push alarms beside polling. This relative path marks an unpublished batch article; replace it only after a real URL exists.
28. Assigned Data-Center Endpoint
Planned canonical: assigned data-center endpoint — Covers assigned data-center endpoint. This relative path marks an unpublished batch article; replace it only after a real URL exists.
29. Signature Rejection
Planned canonical: signature rejection — Covers signature rejection. This relative path marks an unpublished batch article; replace it only after a real URL exists.
Recommended sequence
Phase 1 — establish identity and region
Create the developer application, protect its credentials, and record the data center assigned in the console. Route the credential set to SG, FK, or OR exactly as the current development specification states. Keep the China platform separate. Validate request signing with the official fixed test case before adding business methods.
Phase 2 — bring in one device
Choose the documented provisioning surface, bind only through a path supported by the target device generation, and model both device and channel identifiers. Build a paginated inventory rather than relying on an operator spreadsheet. Do not infer channel count or capabilities that the current device response does not establish.
Phase 3 — receive events safely
Configure only the callback categories needed by the application. The receiver must be Internet-reachable and return HTTP 200 as documented. Queue and idempotency are recommended backend responsibilities. Monitor callback health, but do not publish an invented retry schedule, guaranteed delivery claim, or SLA.
Phase 4 — authorize users and actions
Separate administrator operations from sub-account operations and use only documented permission names. Your product still owns tenant, role, site, and operator authorization. Keep the administrator token on the backend and return only the minimum client credential or data required after your own access check.
Phase 5 — add storage and live operations
Choose snapshot or video retention for the actual incident workflow and subscribed service. Activate and enumerate storage through current methods, then audit created live addresses and schedules. A documented status can be an operational signal; it is not permission to invent public pricing, entitlement, or universal availability.
Phase 6 — choose the application surface
Use mobile or PC OpenSDK, web components, OpenAPI, or Home Assistant according to the user experience and documented responsibility split. Home Assistant Core and the separately maintained component are distinct choices. Verify ownership, naming, releases, device capability, and quota behavior at publication or deployment time.
Official starting points
Next step
Register at Imou Open Platform and complete phases one and two with a single test device. Replace every planned-canonical relative path only after the corresponding article has a real publication URL.
Live-source review date: 2026-08-31. Recheck every source before publication.
Top comments (0)