Pelion Device Management SDKs
Note: Pelion is no longer actively supporting or developing the SDKs. The SDKs will remain on Github, but in new integrations, use the APIs instead. We also recommend that you gradually migrate your existing integrations to the APIs to ensure future compatibility. See the migration guide for more information.
Each SDK has three conceptual interfaces, giving an increasing level of abstraction over the underlying REST API:
- Client: offers direct access to the REST API endpoints.
- Foundation: maps REST resources and HTTP methods onto object-oriented Entities and associated method calls.
- Legacy: the original interface. Some functionality is only available on this interface, but we recommend using the new interfaces whenever possible, for simplicity.
We designed the SDKs for application development. Each method can perform a series of API calls to complete a complex task (workflow) or multiple simple tasks, and they handle the complexity of HTTP requests. For example, use a single SDK call to activate two subscription methods in the APIs - subscription and presubscription. The SDK chains individual API calls, takes the output of one or more API call and uses it as input for the next call.
The full documentation includes prerequisites, interface references and use cases.
There is also language-specific documentation:
|Java||mbed-cloud-sdk-java||Maven Central or JCenter|
|C# / .Net||mbed-cloud-sdk-dotnet||Nuget|
License and contribution
The SDKs are open source (Apache 2 license) and directly available from main artifact repositories (Maven Central, NPM, Nuget, PyPI). Their source code is also available on GitHub, as listed in the table above.
Contributions in the form of GitHub pull requests to any of the public repositories are welcome. Alternatively, you can report feature requests and bugs to the Arm team using GitHub's issues feature.