Device App Test Report

The Device App Test Report API provides endpoints for registering network test reports fromallows mobile applications orand clientnetwork devices.monitoring This functionality enables applicationstools to submit diagnostic data, connectivity metrics, andnetwork performance test results to the serverGATE forsystem. monitoring,This analysis,endpoint enables the collection of comprehensive network metrics including download/upload speeds, latency, jitter, and troubleshootingDNS purposes.response times across different network types like WiFi, 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 is designed tofor collectapplications that perform network testing and processneed networkto diagnosticcentrally datareport fromtheir clientfindings applicationsto andthe devices.GATE monitoring system. This API category is essentialparticularly useful for:

• NetworkMobile Performanceapplications Monitoring:conducting Collecting real-timeperiodic network metricsperformance from end-user devices to monitor connectivity quality and identify potential issuestests
• DiagnosticIoT Datadevices Collectionreporting connectivity metrics

Network monitoring tools: Gatheringsubmitting automated test results Quality assurance systems tracking network performance over time

The endpoint accepts detailed test reports thatincluding includethe network context (type, name), test methodology (download, upload, latency, bandwidth,etc.), packettarget loss,destinations, and connectivitymeasured statusvalues informationwith

appropriate Qualityunits. Assurance:This Enablingdata applicationscan tothen reportbe test resultsanalyzed for network validationperformance trends, troubleshooting, and performanceoptimization benchmarking Troubleshooting Support: Providing technical teams with detailed diagnostic information to resolve connectivity issues efforts.

The API uses standardized abbreviations for network types and test reportstypes typicallyto containensure structuredconsistent data aboutcollection networkacross conditions,different devicereporting information, test parameters,applications and results. This data helps organizations maintain service quality, identify network bottlenecks, and proactively address connectivity problems before they impact users.

Common scenarios include mobile apps performing periodic connectivity checks, IoT devices reporting status, and diagnostic tools submitting comprehensive network analysis results.devices.

---

Endpoints

POST /device_app_test_report/

Description: RegistersSubmits a newnetwork networkperformance test report fromto athe clientGATE device or application.system. This endpoint acceptsallows diagnosticapplications to register the results of network tests they have performed, including speed tests, latency measurements, and connectivity checks. The submitted data includinghelps build a comprehensive picture of network performance metrics,across connectivitydifferent test results, device information,environments and environmentalconnection factors that may affect network performance. Use this endpoint whenever your application completes a network diagnostic test or needs to report connectivity status.types.

Use Cases:

• Mobile applicationsapp reporting WiFi speed test results in different locations

IoT device submitting periodic networkconnectivity health checks Network monitoring tool reporting automated performance reportsmeasurements IoTQuality devicesassurance system logging test results for compliance reporting connectivity status and diagnostic metrics Diagnostic tools uploading comprehensive network analysis results Applications reporting failed connection attempts with detailed error information

Full URL Example:

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

Parameters:

Parameter	Type	In	Required	Description
data	string	body	Yes	JSON-formattedJSON string containing the complete test report data including network metrics, device information, test parameters, timestamps, 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 Type of network connection used for the test wi, mo, bl, et test_type string Yes Type of performance test that was conducted dl, ul, de, jt, dn destination string Yes Target endpoint for the test (URL, hostname, or IP address) Any valid URL/hostname/IP value number Yes Measured test result as a numeric value Any positive number count integer No Number of test iterations performed (default: 1) Any positive integer unit string No Unit of measurement for the test value Kbps, KBps, ms

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 '{
    "data"network_name": "{\Office WiFi 5GHz",
    "device_id\network_type": "wi",
    "test_type":\ "device_12345\dl",
    "destination": "speedtest.net",\
    "app_version\value": 85.7,
    "count":\ 3,
    "2.1.3\unit": ",\"test_type\":\"connectivity_check\",\"timestamp\":\"2024-01-15T14:30:00Z\",\"network_type\":\"wifi\",\"signal_strength\":-45,\"latency_ms\":23,\"download_speed_mbps\":85.2,\"upload_speed_mbps\":42.7,\"packet_loss_percent\":0.1,\"dns_resolution_time_ms\":15,\"connection_success\":true,\"server_endpoint\":\"api.example.com\",\"geolocation\":{\"latitude\":37.7749,\"longitude\":-122.4194},\"device_info\":{\"os\":\"iOS\",\"version\":\"17.1\",\"model\":\"iPhone 14\"}}"Kbps"
  }'

Example Request Body:

{
  "data": "{\"device_id\":\"device_12345\",\"app_version\":\"2.1.3\",\"test_type\":\"connectivity_check\",\"timestamp\":\"2024-01-15T14:30:00Z\",\"network_type\":\"wifi\",\"signal_strength\":-45,\"latency_ms\":23,\"download_speed_mbps\":85.2,\"upload_speed_mbps\":42.7,\"packet_loss_percent\":0.1,\"dns_resolution_time_ms\":15,\"connection_success\":true,\"server_endpoint\":\"api.example.com\",\"geolocation\":{\"latitude\":37.7749,\"longitude\":-122.4194},\"device_info\":{\"os\":\"iOS\",\"version\":\"17.1\",\"model\":\"iPhone 14\"}}"
}

Example Response:

{
  "id": 789456,
  "status"network_name": "received"Office WiFi 5GHz",
  "report_id"network_type": "rpt_2024011514300012345"wi",
  "timestamp"test_type": "2024-01-15T14:30:15Z"dl",
  "processed": false,
  "message"destination": "Testspeedtest.net",
  report"value": successfully85.7,
  registered"count": and3,
  queued"unit": for processing""Kbps"
}

Response Codes:

Status	Description
201	Created - Test report successfully registeredsubmitted and stored
400	Bad Request - Invalid data format or missing required fields
401	Unauthorized - Invalid or missing authentication token
413

Payload Too Large - Test report data exceeds size limits 422 Unprocessable Entity - DataValid format is valid but containsinvalid logicalfield errors 500 Internal Server Error - Server error processing the reportvalues

---

Common Use Cases

Use Case 1: Mobile Speed Test App Connectivity Monitoring

MobileA applicationsmobile canapplication useperforms thisregular endpointspeed tests and reports results to regularly submittrack network performance reports, helping identify connectivity issues across different carriers, locations,locations and networkcarriers. conditions.The Submitapp reportsconducts afterdownload significanttests networkevery eventshour orand onsubmits aresults scheduledwith basis.location context.

Use Case 2: IoT Device Health ReportingMonitoring

Industrial IoT devices canperform report theirperiodic connectivity status,checks signalto strength,ensure reliable communication with cloud services. Devices test DNS response times and communication reliabilitylatency to helpcritical maintainendpoints optimalevery network15 performance and identify devices that may need attention or repositioning.minutes.

Use Case 3: QualityOffice AssuranceNetwork TestingMonitoring

During application testing phases,An automated testmonitoring suitessystem cantests submit comprehensiveinternal network diagnosticperformance reportsby measuring upload/download speeds to validatevarious cloud services, helping IT teams identify performance under various network conditions and identify potential issuesdegradation before release.users are affected.

Use Case 4: UserQuality ExperienceAssurance TroubleshootingTesting

WhenQA usersteams experienceuse connectivityautomated issues,tools to test application performance across different network conditions, submitting jitter and latency measurements to ensure applications canmeet automaticallyperformance generate and submit detailed diagnostic reports to help support teams quickly identify and resolve problems.standards.

Use Case 5: Network Infrastructure MonitoringTroubleshooting

ApplicationsNetwork deployedadministrators acrossdeploy multipletesting locationstools canthat submitcontinuously regularmonitor connection quality to specific destinations, helping identify intermittent connectivity reportsissues to help network administrators monitor infrastructureand performance and identify areas needing improvement.bottlenecks.

---

Best Practices

• DataConsistent StructureTesting ConsistencyIntervals: Maintain a consistent JSON structure within the data parameter across allSubmit test reports at regular intervals to enableestablish properbaseline analysisperformance metrics and trendingidentify trends over time.

• IncludeMeaningful Timestamps:Network Always include accurate UTC timestamps in your test data to enable proper chronological analysis and correlation with network events

Device IdentificationNames: Use consistentdescriptive devicenetwork identifiersnames that allowhelp trackingidentify ofthe individualtesting deviceenvironment performance(e.g., over"Corp_WiFi_Building_A" timerather whilethan respectinggeneric privacynames). requirements

Appropriate Test Counts: When performing multiple test iterations, include the count parameter to provide context for the averaged or aggregated value.

Error Handling: Implement proper retry logic with exponential backoff for failed submissions, especiallyas importantnetwork forconditions network-relatedduring failurestesting might also affect API connectivity.

Data Validation: Validate test data locallyresults before submission to reduce 422 errors and ensure datarealistic qualityvalues (e.g., don't submit negative latency or impossibly high speeds).

BatchDestination ReportingDiversity: ConsiderTest batchingagainst multiple test results when appropriatedestinations to reduceget APIa calls,comprehensive butview ensureof individualnetwork timestampsperformance, areincluding preservedboth local and geographically distributed endpoints.

SensitiveUnit InformationConsistency: AvoidAlways includingspecify personallyunits identifiablefor informationyour (PII)measurements into testensure reports;proper focusdata on technical metricsinterpretation and anonymouscomparison deviceacross characteristics

Rate Limiting: Implement appropriate rate limiting in your application to avoid overwhelming the API, especially for high-frequencydifferent testing scenariostools.

---