Console first live view

Use this path when you want a picture before you write client code. API and SDK integration come after the console check.

Prerequisites

A browser that can open open.imoulife.com.
One physical camera you can power on and reach on site.
You will need the developer AppId later if you continue to OpenAPI.

1. Register and verify the developer account

Open Sign up, complete the form, and keep the credentials. This account is the super administrator. See Create an app and Accounts.

Confirm the data center under Console · My information. Server hosts later use https://openapi-[DataCenter].easy4ip.com.

2. Create an application

Open Create an app. The type can be H5, mobile, web, or PC. Copy AppId and AppSecret from My Application → Application Information. Do not put AppSecret in a client package.

Bind the camera to this developer account. A device that only exists in the consumer app is invisible to OpenAPI. This book documents binding through Add a device. New devices, or devices that just upgraded firmware, may also need the client SDK bind flow in Build a mobile app.

This page does not invent a console “add device” URL. If the console UI shows an add-device entry, use it; the documented contract is still bindDevice plus a bound serial number.

4. Open console live service

Quota and live packages: Console · My resources.

Create a live address, schedule, and H5 page in Console · Live service. Fields such as title, cover, resolution, and encryption are described in Cloud live (HLS).

5. Verify playback

Open the H5 page or the live URL from that console screen. You should see the bound camera. If the player cannot decode the stream, change encoding on the device’s local management page on the LAN, as Choose an integration mode states (H.264 video and AAC audio are typical).

Next: API or SDK integration

Server-side address: First API call and Cloud live from an AppId.
Browser player: Light-app first preview.
Native app: SDK first preview.