1. Scenario overview
Reports and dashboards cover day-to-day charts. Finance and data teams still need detail on the order of a million rows in Excel or CSV, or pushed to a warehouse. A synchronous HTTP call times out, so export and batch jobs run asynchronously: submit the job, get a task_id at once, and the queue builds the file. When it finishes, you get a download link that expires, from object storage. The same pattern fits a batch activation result, a usage detail, or a reconciliation file.
A job can be cancelled, retried, and prioritized. A large job is split and run in parallel. It shares the tenant quota with quotas and rate limits, so one export cannot crowd everyone else out.
2. Core capabilities
Job lifecycle
Queued, running, succeeded, failed, or expired. A failure shows why. You can retry by hand. Past jobs stay available for audit.
Security
The download link is signed and it expires. The file can be password-protected. The action is written to roles and audit.
Into a warehouse
Deliver to the customer’s S3 or OSS, or over SFTP. Webhooks and event subscriptions say when the job is done.
Same numbers as the dashboard
Dashboard metrics and export fields come from the same source, so the screen and the file do not disagree. The definitions match traffic statistics.
3. Typical use cases
- The month-end file for finance: At month end, finance submits a batch export of that month’s data usage and billing detail for every IoT SIM, as CSV, delivered to the finance system’s object storage so operator bills can be checked quickly.
- A nightly increment into the warehouse: BI schedules a job for the early morning. It exports the previous day’s SIM status changes and orders and syncs them to the warehouse, so the operating dashboard can refresh and be cut several ways.
- The result of a large batch suspend: After operations suspends a large set of SIMs, an export lists success, failure, and the reason code. Failed SIMs can be handled again, and the customer can be told.
4. Implementation notes
For a very large extract, export by partition or sync an offline warehouse instead of pulling the same data through the API again and again. Delete expired files on a schedule so storage cost stays down.
5. What you gain
Data export and batch jobs on the SimtoLink IoT Cloud Platform cover enterprise analysis and reconciliation and keep the online API stable. An async job can export on the order of a million rows without blocking the business API. Finance and data can start an export without loading the live system. Delivery straight to object storage sends the file to a warehouse or a BI platform, with no one copying it by hand. The job record and the signed link are what audit and data security ask for while the file is in transit.