How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OneNET Studio Application API

The OneNET Studio application API is the one China Mobile surface with a complete, anonymously readable request-and-response contract. It is an action-dispatched gateway — every call is https://openapi.heclouds.com/{namespace}?action={Action}&version=1, where the namespace is application (application development), common (device management), lwm2m-online or lwm2m-offline. Forty-four operations are documented across devices, products, projects, groups, thing models, device properties and desired properties, thing-model service invocation, device files and scene-linkage rules. Authentication is a signed, time-boxed authorization header (HMAC over et, method, res and version, signature algorithm version 2020-05-29). Every response is a uniform envelope carrying a platform-generated requestId, and business failures arrive as HTTP 200 with success false plus a string error code. China Mobile publishes no OpenAPI for it; the OpenAPI in this repository was transcribed operation by operation from the published reference, with each operation carrying its source page in x-evidence.

OneNET Studio Application API is one of 6 APIs that China Mobile publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include IoT, Device Management, Thing Model, Platform-as-a-Service, and China. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 44 operations across 44 paths, organized into 2 resource areas, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 1.

Requests are made against a single base URL, https://openapi.heclouds.com.

44 operations 44 paths 1 schemas 22 GET22 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1
Base URL
https://openapi.heclouds.com
Authentication
API Key
Resource Areas
2

Authentication & Security 1

OneNET Studio Application API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (onenetAuthorization). By default, every request must be authenticated.

  • onenetAuthorization — OneNET signed authorization token: version=2020-05-29&res=userid/{userid}&et={epoch}&method={md5|sha1|sha256}&sign={signature}, where sign = base64(hmacmethod(…

Paths & Operations 44

Across 44 paths, the API surfaces 44 operations — 22 GET, 22 POST. They span 2 resource areas: Device Management, Application Development. Each is listed below with its method, path, parameters, and response codes.

Device Management 9
POST
/common?action=CreateDevice&version=1
设备创建 (CreateDevice)
CreateDevice body → 200
POST
/common?action=BatchCreateDevices&version=1
设备批量创建 (BatchCreateDevices)
BatchCreateDevices body → 200
POST
/common?action=UpdateDevice&version=1
设备编辑 (UpdateDevice)
UpdateDevice body → 200
POST
/common?action=DeleteDevice&version=1
设备删除 (DeleteDevice)
DeleteDevice body → 200
GET
/common?action=QueryDeviceDetail&version=1
设备详情 (QueryDeviceDetail)
QueryDeviceDetail 2 params → 200
POST
/common?action=MoveProductDevice&version=1
设备转移 (MoveProductDevice)
MoveProductDevice body → 200
GET
/common?action=QuerySystemThingModel&version=1
物模型系统功能点 (QuerySystemThingModel)
QuerySystemThingModel → 200
GET
/common?action=QueryThingModel&version=1
物模型查询 (QueryThingModel)
QueryThingModel 1 param → 200
POST
/common?action=RegistDeviceIdentity&version=1
设备工业标识注册 (RegistDeviceIdentity)
RegistDeviceIdentity body → 200
Application Development 35
GET
/application?action=QueryProductList&version=1
项目集成产品列表 (QueryProductList)
QueryProductList 3 params → 200
GET
/application?action=QueryDeviceList&version=1
项目集成设备列表 (QueryDeviceList)
QueryDeviceList 7 params → 200
POST
/application?action=AddDevice&version=1
项目添加设备 (AddDevice)
AddDevice body → 200
POST
/application?action=RemoveDevice&version=1
项目移除设备 (RemoveDevice)
RemoveDevice body → 200
POST
/application?action=CreateGroup&version=1
分组创建 (CreateGroup)
CreateGroup body → 200
POST
/application?action=DeleteGroup&version=1
分组删除 (DeleteGroup)
DeleteGroup body → 200
POST
/application?action=UpdateGroup&version=1
分组编辑 (UpdateGroup)
UpdateGroup body → 200
GET
/application?action=QueryGroupDetail&version=1
分组详情 (QueryGroupDetail)
QueryGroupDetail 2 params → 200
GET
/application?action=QueryGroupList&version=1
分组列表 (QueryGroupList)
QueryGroupList 6 params → 200
POST
/application?action=AddGroupDevice&version=1
分组设备添加 (AddGroupDevice)
AddGroupDevice body → 200
POST
/application?action=RemoveGroupDevice&version=1
分组设备移除 (RemoveGroupDevice)
RemoveGroupDevice body → 200
GET
/application?action=QueryDeviceDetail&version=1
设备详情 (QueryDeviceDetail)
QueryDeviceDetail 3 params → 200
GET
/application?action=QueryDeviceStatus&version=1
设备状态查询 (QueryDeviceStatus)
QueryDeviceStatus 3 params → 200
GET
/application?action=QueryDeviceStatusHistory&version=1
设备状态记录查询 (QueryDeviceStatusHistory)
QueryDeviceStatusHistory 7 params → 200
POST
/application?action=SetDeviceProperty&version=1
设备属性设置 (SetDeviceProperty)
SetDeviceProperty body → 200
POST
/application?action=QueryDevicePropertyDetail&version=1
设备属性获取 (QueryDevicePropertyDetail)
QueryDevicePropertyDetail body → 200
POST
/application?action=SetDeviceDesiredProperty&version=1
设备属性期望设置 (SetDeviceDesiredProperty)
SetDeviceDesiredProperty body → 200
POST
/application?action=QueryDeviceDesiredProperty&version=1
设备属性期望查询 (QueryDeviceDesiredProperty)
QueryDeviceDesiredProperty body → 200
POST
/application?action=DeleteDeviceDesiredProperty&version=1
设备属性期望删除 (DeleteDeviceDesiredProperty)
DeleteDeviceDesiredProperty body → 200
GET
/application?action=QueryDeviceLog&version=1
设备操作日志查询 (QueryDeviceLog)
QueryDeviceLog 7 params → 200
GET
/application?action=QueryDeviceProperty&version=1
设备最新数据查询 (QueryDeviceProperty)
QueryDeviceProperty 3 params → 200
GET
/application?action=QueryDevicePropertyHistory&version=1
设备属性记录查询 (QueryDevicePropertyHistory)
QueryDevicePropertyHistory 9 params → 200
GET
/application?action=QueryDeviceEventHistory&version=1
设备事件记录查询 (QueryDeviceEventHistory)
QueryDeviceEventHistory 9 params → 200
POST
/application?action=CallService&version=1
设备服务调用 (CallService)
CallService body → 200
GET
/application?action=QueryServiceRecord&version=1
设备服务执行记录查询 (QueryServiceRecord)
QueryServiceRecord 2 params → 200
POST
/application?action=CreateDeviceFile&version=1
设备文件上传 (CreateDeviceFile)
CreateDeviceFile body → 200
GET
/application?action=GetDeviceFile&version=1
设备文件下载 (GetDeviceFile)
GetDeviceFile 1 param → 200
POST
/application?action=DeleteDeviceFile&version=1
设备文件删除 (DeleteDeviceFile)
DeleteDeviceFile body → 200
GET
/application?action=GetDeviceFilesList&version=1
账户文件列表查询 (GetDeviceFilesList)
GetDeviceFilesList → 200
GET
/application?action=GetDeviceFileSpace&version=1
账户文件存储空间查询 (GetDeviceFileSpace)
GetDeviceFileSpace → 200
GET
/application?action=GetDeviceFileCount&version=1
账户设备文件数量查询 (GetDeviceFileCount)
GetDeviceFileCount 2 params → 200
POST
/application?action=CreateSceneRule&version=1
场景联动规则创建 (CreateSceneRule)
CreateSceneRule body → 200
GET
/application?action=QuerySceneRuleDetail&version=1
场景联动规则详情 (QuerySceneRuleDetail)
QuerySceneRuleDetail 2 params → 200
GET
/application?action=QuerySceneRules&version=1
场景联动规则列表 (QuerySceneRules)
QuerySceneRules 3 params → 200
GET
/application?action=QuerySceneLog&version=1
场景联动触发日志 (QuerySceneLog)
QuerySceneLog 6 params → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ResponseEnvelope (5 properties). Each schema is shown below with its type and property counts.

ResponseEnvelope
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

china-mobile-onenet-studio-openapi.yml Raw ↑

Other APIs China Mobile publishes across the network.

OneNET Voice Call Service (VCS) API
OneNET IoT Open Platform API
China Mobile IoT Card Capability Open Platform API
China Mobile Communication Capability Open Platform
China Mobile Internet Capability Open Platform
Where this information came from

This is an independent, third-party profile of OneNET Studio Application API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.