Integration overview
You can integrate the IoT Mobile Connection Package service into your system to manage credentials for new IoT cards, query orders, retrieve card information, and monitor card status in real time. This integration allows for efficient operation and intelligent management of your IoT cards. This topic outlines the IoT Mobile Connection Package service OpenAPI and its various integration solutions.
Introduction to OpenAPI
Alibaba Cloud OpenAPI is a set of interfaces that allows developers to programmatically access and manage Alibaba Cloud services. It provides automated and customized solutions. To help developers quickly and efficiently learn and use the OpenAPI of cloud products, Alibaba Cloud provides the OpenAPI Portal. The portal integrates powerful features such as intelligent OpenAPI search, detailed document viewing, instant online debugging, easy software development kit (SDK) acquisition, code sample referencing, error diagnosis tools, and call statistics analysis. Using the OpenAPI Portal, you can seamlessly connect to and call the OpenAPI of all Alibaba Cloud products. You can also visually review API requests and their response details to accelerate your development process. For more information, see What is OpenAPI?.
Version guide
The API list for online debugging is for version 2021-05-20. This string is the API version number, not a date. The list is continuously updated and always shows the latest public API data. To learn how to view API versions, see View API versions.
Version number |
Description |
Recommended |
Online debugging
The IoT Mobile Connection Package service supports API debugging in the Alibaba Cloud OpenAPI Portal. Before you start debugging, make sure that you understand the API version, endpoint description, and API parameters.
Debugging entry point
The entry point for API debugging is: IoT Mobile Connection Package_API Debugging.
Endpoint description
Endpoints are the entry points for accessing Alibaba Cloud services. They are divided into public endpoints and VPC endpoints.
Public endpoints are accessible globally.
VPC endpoints are accessible only from within the corresponding Alibaba Cloud region over a VPC network. VPC endpoints provide the following benefits:
High security: VPC endpoints can be accessed only from within a VPC. This provides greater security and privacy.
Faster response time: Because VPC endpoints run on the internal VPC network, their response time is usually faster than that of public endpoints. They can also help you avoid issues such as Internet latency and bandwidth limitations.
Lower costs: VPC endpoints use internal network communication, which reduces reliance on external traffic. This can effectively lower the costs that are incurred from using public bandwidth.
When you select an endpoint, choose one that is geographically closest to your users or business. This reduces network latency and improves data transmission speed and application response time. For example, if your main user base is in Hangzhou, the Hangzhou region endpoint is a better choice.
To view the endpoints for the IoT Mobile Connection Package service, see the List of Service Regions.
User identity
When you log on to the OpenAPI Portal with your Alibaba Cloud account, OpenAPI uses your Alibaba Cloud account by default for online debugging. An Alibaba Cloud account has access permissions to all APIs, which poses a high security threat. We recommend that you create and use a Resource Access Management (RAM) user for API access or daily O&M. You must grant the RAM user the required permissions for the IoT Mobile Connection Package service before you make API calls. For more information, see Access control.
User identity |
Support status |
Support |
|
RAM user (Recommended) |
Supported |
RAM role (Recommended) |
Support |
More information
Integration methods
We recommend that you use an SDK. This is the easiest integration method and provides the best support for calling OpenAPI.
Alibaba Cloud SDK
Alibaba Cloud provides SDKs for multiple programming languages, such as Java, C#, Go, Python, Node.js/TypeScript, PHP, and C++. Developers can integrate an SDK and call OpenAPI directly using the methods that are exposed by the SDK. The SDK encapsulates the signature logic, timeout mechanism, and retry mechanism. It also provides request and response objects, which simplifies development. For more information about Alibaba Cloud SDKs, see Alibaba Cloud SDK.
You can use the IoT Mobile Connection Package service SDK to call OpenAPI. For information about supported languages and how to install dependencies, see IoT Mobile Connection Package Service SDK.
Alibaba Cloud CLI
Alibaba Cloud Command Line Interface (CLI) lets you use the
aliyuncommand in a terminal to interact with Alibaba Cloud services and manage your cloud resources. For more information about Alibaba Cloud CLI, see What is Alibaba Cloud CLI?.Alibaba Cloud CLI does not currently support calling the OpenAPI of the IoT Mobile Connection Package service.
Terraform
Terraform is an open source tool that you can use to securely and efficiently preview, configure, and manage cloud infrastructure and resources. Its operating mechanism is similar to that of Alibaba Cloud Resource Orchestration Service (ROS). Terraform converts templates into internal data and then makes OpenAPI calls. For more information, see What is Terraform?.
Terraform does not currently support calling the OpenAPI of the IoT Mobile Connection Package service.
Resource Orchestration Service (ROS)
Resource Orchestration Service (ROS) is an Alibaba Cloud service that simplifies cloud resource management. Developers and administrators can write templates to define the required Alibaba Cloud resources, such as ECS instances and ApsaraDB RDS database instances, and the dependencies between them. The ROS orchestration engine automatically creates and configures all resources based on the template to achieve automated deployment and O&M. For more information, see What is Resource Orchestration Service?.
ROS does not currently support calling the OpenAPI of the IoT Mobile Connection Package service.
Custom encapsulated API calls
If you make native HTTP calls, you must implement the signature algorithm, build a custom request, and initiate the HTTP call. For more information about the signature mechanism, see IoT Mobile Connection Package API Reference and V3 request body & signature mechanism.
Notes
If an error is reported after you make an API call, check the request parameters and their values based on the returned error code. For more information, see Error codes.
You can also record the RequestID that is returned from the call or the SDK error message and use the Alibaba Cloud OpenAPI Diagnostic Platform for self-service diagnosis.