1. Home
  2. Docs
  3. IoTGtw API Samples
  4. Provisioning API (Manage Account, Devices, Service Templates, Endpoint Profiles)
  5. Analytics

Analytics

Count the total number of devices on the account, group the result by device state and service template
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Note:
When performing device count operation, the group_by attribute can be any combination of ["state", "service_template_id", "service_access_point", "device_app_protocol"];
Count the total number of devices configured with the specified service_template_id group by device state
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Count the total number of devices using the specified SAP
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Analyse the total number of messages in the “pending” queue of all devices
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Note:
When performing messaging count analytics granular count operation can be requested by specifying whether to count all queues, specific queues or specific queues and uplink or downlink traffic. The count operation must be specified as one of the following: [“all_queues” or “pending” or “pending_uplink” or “pending_downlink” or “shipped” or “shipped_uplink” or “shipped_downlink” or “failed” or “fiailed_uplink” or “failed_downlink”]
The group_by attribute can be any combination of [“service_template_id”, “service_access_point”, “device_app_protocol”, “msg_submit_status”, “delivery_type”, “device_tx_protocol”, “transaction_type”]
Analyse the total number of messages in “all_queues” of all devices
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Note:
• When performing messaging count analytics granular count operation can be requested by specifying whether to count all queues, specific queues or specific queues and uplink or downlink traffic. The count operation must be specified as one of the following: [“all_queues” or “pending” or “pending_uplink” or “pending_downlink” or “shipped” or “shipped_uplink” or “shipped_downlink” or “failed” or “fiailed_uplink” or “failed_downlink”]
• The group_by attribute can be any combination of [“service_template_id”, “service_access_point”, “device_app_protocol”, “msg_submit_status”, “delivery_type”, “device_tx_protocol”, “transaction_type”]
Analyse the total number of messages in “all_queues” of all devices that were sent/received within the specified start and end date
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Analyse the total number of messages in the “shipped” queue of a specific device that were sent/received within the specified start and end date.
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Sample Response

Analyse the total number of messages that matches the specified criteria (Example of supported message filter criteria).
Property Description
Resource URL /customer/v1/{customer_id}/service_provisioning/count
Method POST
Body Count Object
Sample Request

Note:
• When performing messaging count analytics granular count operation can be requested by specifying whether to count all queues, specific queues or specific queues and uplink or downlink traffic. The count operation must be specified as one of the following: [“all_queues” or “pending” or “pending_uplink” or “pending_downlink” or “shipped” or “shipped_uplink” or “shipped_downlink” or “failed” or “fiailed_uplink” or “failed_downlink”]
• The group_by attribute can be any combination of [“service_template_id”, “service_access_point”, “device_app_protocol”, “msg_submit_status”, “delivery_type”, “device_tx_protocol”, “transaction_type”]
Was this article helpful to you? Yes No

How can we help?