Device App Test Report

Endpoints Summary

Method Path Swagger POST /device_app_test_report/ Swagger ↗

---

The Device App Test Report API allowsenables mobile applications and networkdesktop monitoring toolsapplications to submit network performance test results to the GATE system.platform. This endpoint enablesallows thedevelopers collectionto ofregister comprehensivetest network metricsdata including download/upload speeds, latency, jitter, and DNS response times across different network types like WiFi, Mobile,mobile, Bluetooth, and Ethernet.

Base URL: https://gate.zequenze.com/api/v1

Authentication: All endpoints require a Bearer token:

Authorization: Bearer <your-api-token>

---

Overview

The Device App Test Report API provides a centralized way to collect and store network performance metrics from client applications. This API is designed for applications that perform network testingdiagnostics, speed tests, or connectivity monitoring and need to centrally report their findings to thea GATEcentral monitoringanalytics system.platform.

This

Key API is particularly useful for:Features:

• Support for multiple network types (WiFi, Mobile, Bluetooth, Ethernet)

Multiple test types including bandwidth, latency, jitter, and DNS performance Flexible destination targeting (URLs, hostnames, IP addresses) Standardized units and result formatting Batch test result reporting with count tracking

Common Integration Scenarios:

Mobile applicationsapps conductingperforming periodic network performanceconnectivity tests Network IoTmonitoring devicestools reporting connectivityperformance metrics IoT Network monitoring toolsdevices submitting automatedconnectivity testhealth resultsdata Desktop applications measuring network quality Quality assurance systemstools trackingvalidating network performance over time

The endpoint accepts detailed test reports including the network context (type, name), test methodology (download, upload, latency, etc.), target destinations, and measured values with appropriate units. This data can then be analyzed for network performance trends, troubleshooting, and optimization efforts.

The API uses standardized abbreviations for network types and test types to ensure consistent data collection across different reportingclient applications and devices.implementations.

---

Endpoints

POST /device_app_test_report/

Description: Submits a network performance test reportresults from client applications to the GATE system.platform. This endpoint allowsaccepts applicationstest data including network performance metrics, test metadata, and result values. Use this endpoint when your application has completed network tests and needs to registerreport the results offor networkanalytics, testsmonitoring, theyor havetroubleshooting performed, including speed tests, latency measurements, and connectivity checks. The submitted data helps build a comprehensive picture of network performance across different environments and connection types.purposes.

Use Cases:

• Mobile app reporting WiFi speed test apps reporting download/upload results in different locations

IoT device submitting periodic connectivity health checks Network monitoring tooltools submitting latency measurements IoT devices reporting automatedconnectivity performancehealth measurementsmetrics Quality assurance systemapplications loggingvalidating testnetwork resultsperformance forDiagnostic compliancetools reportingmeasuring DNS response times

Full URL Example:

https://gate.zequenze.com/api/v1/device_app_test_report/

Parameters:

Parameter	Type	In	Required	Description
data	string	body	Yes	JSON string containing the complete test report data with network type, test type, destination, and results

Request Body Schema:

Field	Type	Required	Description

Allowed Values network_name string No Name of the current network (e.g., "Office WiFi", "Verizon LTE") Any string network_type string Yes TypeNetwork oftype networkcode: connection'wi' used(WiFi), for'mo' the(Mobile), test'bl' wi,(Bluetooth), mo,'et' bl, et(Ethernet) test_type string Yes TypeTest oftype performancecode: test'dl' that(Download), was'ul' conducted(Upload), dl,'de' ul,(Delay), de,'jt' jt,(Jitter), dn'dn' (DNS response time) destination string Yes Target endpoint for the testtest: (URL, hostname, or IP address) Any valid URL/hostname/IPaddress value number Yes MeasuredNumeric test result as a numeric value Any positive number count integer No Number of test iterations performed (default:useful 1)for Anyaveraged positive integerresults) unit string No Unit of measurementmeasurement: for'Kbps' the(Kilobits/sec), test'KBps' value(Kilobytes/sec), Kbps,'ms' KBps, ms(Milliseconds)

Network Type Codes:

wi = WiFi mo = Mobile (cellular) bl = Bluetooth et = Ethernet

Test Type Codes:

dl = Download speed test ul = Upload speed test de = Delay/latency test jt = Jitter measurement dn = DNS response time test

cURL Example:

curl -X POST "https://gate.zequenze.com/api/v1/device_app_test_report/" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "network_name": "Office WiFi 5GHz"WiFi",
    "network_type": "wi",
    "test_type": "dl",
    "destination": "speedtest.net"example.com",
    "value": 85.95.7,
    "count": 3,
    "unit": "Kbps"
  }'

Example Response:Request Bodies:

Download Speed Test:

{
  "network_name": "OfficeHome WiFi 5GHz",
  "network_type": "wi",
  "test_type": "dl",
  "destination": "cdn.speedtest.net",
  "value": 85.150.5,
  "count": 5,
  "unit": "Kbps"
}

Mobile Network Latency Test:

{
  "network_name": "T-Mobile 5G",
  "network_type": "mo",
  "test_type": "de",
  "destination": "8.8.8.8",
  "value": 45.2,
  "count": 10,
  "unit": "ms"
}

DNS Response Time Test:

{
  "network_type": "et",
  "test_type": "dn",
  "destination": "google.com",
  "value": 12.8,
  "count": 1,
  "unit": "ms"
}

Example Response (201 Created):

{
  "id": 12847,
  "network_name": "Office WiFi",
  "network_type": "wi",
  "test_type": "dl",
  "destination": "speedtest.example.com",
  "value": 95.7,
  "count": 3,
  "unit": "Kbps",
  "timestamp": "2024-01-15T14:32:18Z",
  "status": "processed"
}

Response Codes:

Status	Description
201	Created - Test report successfully submitted and storedregistered
400	Bad Request - Invalid data format or missing required fields
401	Unauthorized - Invalid or missing authenticationAPI token
422	Unprocessable Entity - Valid formatJSON but invalid field values

500 Internal Server Error - Server processing error

---

Common Use Cases

Use Case 1: Mobile Speed TestTesting AppApplication

A mobile applicationapp that performs regularperiodic network speed tests and reports results to trackmonitor networkcarrier performance across different locations and carriers.times.

The

# app conductsReport download testsspeed everytest
hourPOST and submits results/device_app_test_report/ with locationmobile context.network download data

Use Case 2: IoT Device HealthConnectivity Monitoring

Industrial IoT devices performthat periodicneed to report their network connectivity checksquality tofor ensureremote reliablemonitoring communicationand troubleshooting purposes.

# Report connectivity health metrics
POST /device_app_test_report/ with cloudlatency services. Devices testand DNS response timesdata
and latency to critical endpoints every 15 minutes.

Use Case 3: OfficeEnterprise Network MonitoringQuality Assurance

AnCorporate automatedapplications monitoringthat system tests internalvalidate network performance byacross measuringoffice upload/download speedslocations to variousensure cloudadequate services,connectivity helpingfor ITbusiness teamsapplications.

identify

# Report comprehensive network tests
POST /device_app_test_report/ with WiFi/Ethernet performance degradationdata
before users are affected.

Use Case 4: QualityGaming AssuranceApplication TestingLatency Monitoring

QAGaming teamsplatforms usethat automatedmeasure toolsand report network latency to testgame applicationservers for matchmaking and performance acrossoptimization.

different

# networkReport conditions,game submittingserver latency
POST /device_app_test_report/ with jitter and latencydelay measurements
to ensure applications meet performance standards.

Use Case 5: Network TroubleshootingDiagnostic Tools

NetworkDiagnostic administrators deploy testing toolsapplications that continuouslyperform monitorcomprehensive connectionnetwork qualitytests and need to specificcentralize destinations,results helpingfor identify intermittent connectivity issuesanalysis and performancereporting.

bottlenecks.

# Report multi-test diagnostic results
POST /device_app_test_report/ with various test types and destinations

---

Best Practices

• Consistent Testing Intervals: Submit test reports at regular intervals to establish baseline performance metrics and identify trends over time.

MeaningfulStandardize Network Names: Use descriptiveconsistent networknaming namesconventions thatfor helpnetwork_name identifyto theenable testingbetter environmentanalytics (e.g., "Corp_WiFi_Building_A"Office_WiFi_5GHz" rather than genericvarying names).formats)

AppropriateBatch TestRelated CountsTests: When performing multiple test iterations,types includeon the same network, submit separate reports for each test type to maintain data clarity

Include Test Counts: Always specify the count parameter when averaging multiple test runs to provide context for theresult averagedreliability

Use Appropriate Units: Match units to test types - use 'ms' for latency/jitter/DNS tests, 'Kbps' or aggregated'KBps' value.for throughput tests

Handle Network Transitions: Be aware that network_type may change during testing on mobile devices; submit separate reports when network switches occur

Error Handling: Implement retry logic for failed submissions, asespecially networkon conditionsmobile duringnetworks testingwhere mightconnectivity alsomay affectbe API connectivity.intermittent

Data Validation: Validate test results before submission to ensureavoid realisticreporting obviously invalid values (e.g., don't submit negative latency orlatency, impossibly high speeds).

DestinationPrivacy DiversityConsiderations: TestBe against multiple destinations to get a comprehensive viewmindful of network performance, including bothsensitive localinformation andin geographicallynetwork_name distributedor endpoints.

destination fields,

Unit Consistency: Always specify unitsespecially for yourenterprise measurements to ensure proper data interpretation and comparison across different testing tools.deployments

---