xTalk SDK Documentation
The xTalk SDK 1.0.0 customer documentation was released on July 20, 2026. It is intended for developers integrating device access, Mesh, voice, file, and OTA capabilities into their own Android or iOS applications.
:::info Delivery scope This site publishes customer integration documentation. It does not include SDK source code, AARs, Swift packages, repository credentials, or firmware. Use the formal customer delivery manifest for binaries, dependencies, checksums, and access details. :::
Start by platform
- Android SDK 1.0.0 integration overview: BLE, UART, authentication, initialization, Mesh, low-latency PTT, channel presence, OTA, and offline STT.
- iOS SDK 1.0.0 integration overview: BLE, authentication, Mesh, low-latency PTT, file and image transfer, and OTA.
Recommended reading order
- Read the integration overview and requirements for your platform.
- Establish the BLE or UART physical link.
- Authenticate the device; on Android, continue with device initialization.
- Add Mesh, PTT, file transfer, OTA, or STT as needed.
- Use the API coverage matrix to verify the formal customer API and implement error handling from the errors and FAQ page.
Documentation architecture
| Layer | Android | iOS |
|---|---|---|
| Device transport | BLE, UART, and RadioTransport | BLE and customer transport adapters |
| Device admission | Device Auth and Device Init | Device Auth; business initialization remains in the customer app or a separately delivered product |
| Product capabilities | Mesh, low-latency PTT, channel presence, OTA, and offline STT | Mesh, low-latency PTT, file and image transfer, and OTA |
| API verification | API reference, coverage matrix, end-to-end example, errors, and FAQ | API reference, coverage matrix, end-to-end example, errors, and FAQ |
Original documentation package
Download the xTalk SDK 1.0.0 customer documentation ZIP
The website uses stable English URLs while preserving Chinese and English content and platform navigation. The ZIP retains the original delivery folders and filenames for offline use and archival.
Security and compatibility
- Application, SDK, and device firmware versions are managed independently.
- Never publish authentication responses, customer repository credentials, or business keys in logs or web pages.
- APIs marked
Advancedare intended for transport or protocol developers; regular applications should prefer theRecommendedpath. - File and voice transport must not be assumed to be an end-to-end secure channel; customer applications must add protection for sensitive business data.