1. Scenario overview
The open API is the capability layer the IoT SIM platform exposes to business systems. Standardized REST APIs let ERP, CRM, customer-service tools, and a platform you build yourself call SIM management, data plans, usage, orders, and users, so the work runs without rekeying. Operator connectivity is the platform talking to the operator. The open API is the platform exposing those capabilities to your systems.
AccessKey/SecretKey authentication, request signatures against tampering, IP allowlists, rate limits, and call logs are included. Documentation, multi-language SDKs, and a sandbox come with the APIs. Integrate once with the platform and you get the full business surface, without handling operator differences yourself.
2. API groups
SIM management API
Activate a SIM, suspend and resume, change the data plan, look up SIM details, and run batch actions. Sync and async modes are both available. Large batches can return through an async callback, which fits high concurrency and bulk activation.
Data plan and usage APIs
List plans, order a plan, query usage, and pull usage detail. Query by SIM, by project, or by time range when you monitor usage or reconcile billing.
Order and user APIs
Create, query, and refund orders. Register users, bind a SIM, and manage permissions. Connect your own systems so the order, the activation, and the user stay in one loop.
Security and documentation
AccessKey/SecretKey authentication, request signatures against tampering, an IP allowlist, and a call-rate limit. The documentation includes request and response examples and error codes, plus online debugging, a Postman collection, and SDKs for Java, Python, and PHP.
3. How to connect
4. Open API and operator connectivity
These are two layers of the platform. The differences:
| Dimension | Open API | Operator connectivity |
|---|---|---|
| Who you connect | Your business systems (ERP, CRM, or a platform you build) | Operator systems (China Mobile, China Unicom, China Telecom) |
| What it does | Exposes platform capabilities to your company | The platform talks to the operator |
| What you have to handle | Call the API to automate SIM management, plans, and usage | Nothing. The platform wraps it |
| Typical calls | Activation, suspend and resume, plan changes, usage lookup, order management | Operator activation APIs, status sync, usage pull |
Connect to the platform API and you get the full business surface. The platform talks to the operators and hides the differences between them.
5. Where teams use it
- ERP and CRM: Sync SIM management and orders through the API so staff do not enter the same record twice.
- Customer service: When a caller gives a SIM number, the desk looks up status, plan, and usage and answers faster.
- A platform you build: Pull SIM, plan, and usage data into your own IoT console, and present and operate it the way your team works.
6. What changes in daily operations
The open API is how SIM work gets automated. System integration connects ERP, CRM, and customer service and cuts manual steps. Fast onboarding comes from documentation, multi-language SDKs, and a sandbox you can test in. Security stays in your control through authentication, signatures, rate limits, and an IP allowlist. One integration covers the platform, so operator differences stay inside SimtoLink.
7. How to put it in place
Prove the calls in the sandbox before you request production keys. Store authentication keys carefully and rotate them. Rate limits can be set per API and per account so a client cannot abuse the quota. Call logs are what you use to troubleshoot and to audit. The APIs cover SIM management, data plans, usage, and orders. Paired with payment integration, an order can move through payment and activation without a handoff.