See API performance from your users’ side of the connection. Find slow requests, separate network delays from server time and get notified when errors become an incident.
iOS, tvOS & Android · PRO & ENTERPRISE · Hosted in Switzerland
Illustrative data
A slow API call is not always a slow backend. Break the round trip into phases before you decide what to fix.
GET /products840 msSend Server-Timing: total;dur=580 to help refine the server phase for a single-transaction request.
Illustrative timing breakdown
Spotted a slow request in a bug report, crash or UI test recording? Choose “Analyze request” to open its operation here.
Set an error-rate threshold for a backend environment. Appelium looks for convincing evidence before interrupting your team.
Evaluated every minute over the latest five minutes of received metrics. Detection depends on traffic volume and data arrival, not a guaranteed one-minute alert.
An error-rate threshold crossed with statistical confidence, not just a single failed request.
Incident and recovery notifications, with a link back to Appelium.
Illustrative incident
Latency trends help you investigate performance. Network alarms currently trigger on error rates, not response time.
Narrow the scope, find the affected requests and connect backend trouble to what happened in the app.
Break metrics down by operation, host, backend environment, app version, platform or network interface. Compare where errors and delays concentrate.
Separate test requests from non-test traffic in the workspace network view, or include both when investigating the bigger picture.
Enable diagnostic network logs to inspect requests alongside bug reports, crashes and handled errors. Metrics do not require full payload capture.
Enable monitoring in the SDK. URLSession powers collection on iOS and tvOS; add the Appelium EventListener to your OkHttp client on Android.
val client = OkHttpClient.Builder()
.eventListenerFactory(
AppeliumOkhttpEventListener.Factory()
)
.build()A fast request can still be part of a slow flow. Use performance traces to time complete app operations, not just their network calls.
Get started: iOS, tvOS, Android · Network monitoring & Server-Timing guide
Appelium measures requests from your mobile app, including DNS, connection setup, sending the request and receiving the response. A fast server can still feel slow to a user on a poor connection. These client-side measurements complement your server monitoring rather than replace it.
Choose a backend environment, an error category (client, business, server or all errors) and an error-rate threshold. Appelium evaluates the latest five minutes of received metrics every minute. A new alarm requires statistical confidence that the error rate exceeds your threshold; low traffic can delay detection. Latency is available for analysis, but does not currently trigger alarms.
No. Network metrics and full request logs are separate capabilities. On Android, the OkHttp EventListener captures metrics; the optional interceptor adds headers and payloads to diagnostic logs. The SDK also provides filtering and obfuscation hooks for captured network logs.
Network monitoring supports iOS and tvOS through URLSession, and Android through the Appelium OkHttp integration. Network monitoring and alarming are available on PRO and ENTERPRISE plans.
Find the slow calls. Understand the failures. Bring the right people in.
Trusted by

A strongly typed, bidirectional and low-latency channel between the app and XCUITest, with round-trips of about 3 ms.
A robust, scalable pattern for structuring UI tests: reusable screen verification, readable test cases, and statically typed flows and interactions.
How SnapshotQuery in AppeliumTests makes XCUITest element queries about 1,000 times faster while making tests more stable.
Be the first one to know about all the exciting engineering posts and product announcements.