SimtoLink: The console exports a month's data bill
Open API integration is the capability layer of an IoT-card management platform toward enterprise business systems. It provides standard RESTful interfaces so ERP, CRM, customer-service systems, in-house platforms, and similar systems can call card management, plans, data usage, orders, users, and related capabilities, for business automation and system integration. Unlike operator integration, which is the platform talking to the operator underneath, an open API is the platform opening its capabilities to enterprise systems.
Interface capabilities and security
The platform supports AccessKey/SecretKey authentication, request signatures against tampering, an IP allowlist, call rate limits, and call logs, and it provides full API documentation, SDKs in several languages, and a sandbox. An enterprise only needs to integrate with the platform API to get the full set of business capabilities, without handling differences among operators.
The card-management API supports activation, suspend and resume, plan changes, card-information queries, and batch operations, in both synchronous and asynchronous modes. Large batches can call back asynchronously. The plan and usage API supports the plan list, plan ordering, usage queries, and usage detail, by card, by project, and by time range. The order and user API supports order creation, query, and refund, plus user registration, card binding, and permission management, and can close the loop of orders, activation, and users with the enterprise's own business systems.
Security includes AccessKey/SecretKey authentication, request signatures against tampering, an IP allowlist, and call-rate limits. The full API documentation includes request and response examples and error-code explanations, and supports online debugging, a Postman collection, and SDKs in languages such as Java, Python, and PHP. The integration path is to apply for keys, test in the sandbox, set up signature authentication, go into production, and then monitor and operate.
How this differs from operator integration
Open APIs and operator integration are two layers of the platform. The counterpart of an open API is an enterprise business system, such as ERP, CRM, or an in-house platform. Its job is to open the platform's business capabilities to the enterprise. Typical capabilities include activation, suspend and resume, plan changes, usage queries, and order management. The counterpart of operator integration is an operator system, such as China Mobile, China Unicom, or China Telecom. Its job is communication between the platform and the operator underneath. Typical capabilities include the operator activation interface, status sync, and usage pull. What the enterprise cares about is calling the API to automate card management, plans, and usage, without handling differences among operators.
An enterprise only needs to integrate with the platform API to get the full set of business capabilities. The platform handles communication with operators and hides differences among them.
Typical scenarios and rollout
Enterprise ERP and CRM use the API for card management and order sync, which avoids repeated manual entry. A customer-service system calls the card-information query API so that, when a user reports a card number, staff can quickly retrieve card status, plan, and usage. An enterprise's own IoT management platform can use the API to obtain card, plan, and usage data for a customized display and operations.
The SimtoLink IoT cloud platform open-API plan helps enterprises automate card management: seamless integration with ERP, CRM, and customer-service systems reduces manual work; full documentation, multi-language SDKs, and a sandbox support joint testing; authentication, signatures, rate limits, and an IP allowlist protect calls; and the enterprise only integrates with the platform API, without handling differences among operators.
Test first in the sandbox, and apply for production keys only after that passes. Authentication keys should be kept carefully and rotated regularly. Rate limits can be set by interface and by account to prevent abuse. Call logs help with troubleshooting and audit. The API covers the main business scenarios of card management, plans, usage, and orders. Together with payment integration, it can automate the full flow of order, payment, and activation.