Device Network and Identity Information (Coming Soon)
WLTE OpenAPI will provide device network and identity information through standard REST APIs, allowing your system to read LTE, IMEI, and band data through a consistent interface.
Capability preview
These endpoints are not yet available. When they are released, this section will provide complete paths, fields, and usage rules.
Planned Capabilities
| Capability | Purpose | Current Status |
|---|---|---|
| Get LTE Network Information | Read cellular-network state for connectivity diagnosis and operational views | Coming soon |
| Get IMEI | Read the cellular module identity for asset identification | Coming soon |
| Set LTE Bands | Set preferred LTE bands within the range explicitly supported by the device | Coming soon |
Design Principles
- Expose explicit REST resources with standardized fields.
- Determine endpoint availability from the device type, cellular module, and firmware capabilities.
- Include collection time in query results so callers can evaluate data freshness.
- Represent information from different cellular modules with a consistent data structure.
- Validate network-configuration parameters and prevent concurrent configuration changes on the same device.
Data Sources and Boundaries
The planned response fields are based on the official SIMCom A76XX Series AT Command Manual and are converted by OpenAPI into stable REST fields. Callers do not need to send, parse, or understand AT commands.
- Expose only values that the cellular module returns explicitly and that can be standardized reliably.
- Convert vendor-specific codes into explicit enums or physical units before release. Raw values with unconfirmed units or meaning will not become official fields.
- Available fields depend on the device model, regional variant, and firmware capabilities. Actual availability is determined by device capabilities and endpoint responses.
- Device identity information such as IMEI is returned only to an API Client authorized to access that device.
References: SIMCom A76XX Official Technical Documents, A7672X Model and Band Information
Currently Available Alternatives
These endpoints are not yet available. Continue using the following endpoints for device online state and existing peripheral data:
After Release
When these endpoints become available, this section will document:
- Request methods and final paths
- Required permissions
- Request and response fields
- Device capability checks
- Rate-limit and retry rules
- Error codes and compatibility scope