NebularStack
Website

Subscriber Telemetry API

Subscriber Counts

GET
/v1/subscribers/count
(subscriber)

Subscriber Current Total Count
Service
subscriber

Data Usage

The following API definitions describe how to perform data usage queries. These queries are restricted. Please refer to Subscriber Telemetry documentation for more information relating their use.

Query Restrictions:

Resolution /
Aggregation.
Max time range.

Available Data.

Hourly

128 days.

5 years.

Daily

128 days.

5 years.

Weekly

114 weeks.

5 years.

Monthly

60 months.

5 years.

Yearly

5 years.

5 years.

All data usage records are available in all timezones.

POST
/v1/subscriber/{subscriber_id}/data/{aggregation}
(telemetry)

Subscriber Account data usage.
Service
telemetry
POST
/v1/subscriber/virtual/{virtual_id}/data/{aggregation}
(telemetry)

Virtual Server data usage.
Service
telemetry
POST
/v1/subscriber/client/{client_id}/data/{aggregation}
(telemetry)

Virtual Server Client data usage.
Service
telemetry
POST
/v1/subscriber/service/{service_id}/data/{aggregation}
(telemetry)

Service Profile data usage.
Service
telemetry
POST
/v1/subscriber/profile/{profile_id}/data/{aggregation}
(telemetry)

Subscriber Profile data usage.
Service
telemetry

Top Subscribers by Data Usage

POST
/v1/subscriber/topusers
(telemetry)

List Top Subscribers by Usage
Service
telemetry

Credit Usage

GET
/v1/subscriber/{subscriber_id}/credit/status
(telemetry)

Subscriber Current Credits Usage
Service
telemetry

Active/Inactive Subscriber Counts

POST
/v1/subscriber/count
(telemetry)

Subscriber Active/Inactive Count
Service
telemetry

Event Logs

The following API definitions describe how to query subscriber event logs. Please refer to Subscriber Telemetry - Event Logs documentation for more information relating their use.

Events are only retained for up to 2 weeks.

GET
/v1/subscriber/{subscriber_id}/events
(telemetry)

List of Events.
Service
telemetry
GET
/v1/subscriber/{subscriber_id}/event/{event_id}
(telemetry)

Get Event.
Service
telemetry

Caller Data Records (CDR)

The following API definitions describe how to query subscriber CDR logs. Please refer to Subscriber Telemetry - Caller Data Records documentation for more information relating their use.

The CDR list endpoint supports both GET and POST:

  • GET returns the CDRs for the last 5 days. It takes no date parameters; any that are supplied are ignored.

  • POST returns the CDRs for an explicit date range, supplied in the request body as start_time and end_time (both required). end_time must be after start_time and the range must not exceed 32 days.

Data is retained for 5 years.

GET
/v1/subscriber/{subscriber_id}/cdr/records
(telemetry)

CDR List for one subscriber (last 5 days).
Service
telemetry
POST
/v1/subscriber/{subscriber_id}/cdr/records
(telemetry)

CDR List for one subscriber (date range).
Service
telemetry
GET
/v1/subscriber/cdr/record/{cdr_id}
(telemetry)

CDR record.
Service
telemetry

Subscriber Reports

A subscriber report contains information about all subscribers within a the provided domain context. The available report types are: Subscriber Usage; Subscriber Credit Usage; and Active/Inactive Subscribers.

The following API definitions describe how to query subscriber reports.

POST
/v1/subscriber/report
(telemetry)

Subscriber Report.
Service
telemetry