API Call in a SIM test
Send an HTTP request over the SIM's data connection and check the response status, body, headers and timing.
Test your APIs exactly as a mobile client reaches them, through the mobile network. Set the method, headers and body, then assert on the response and read the full timing breakdown, from the DNS lookup to the last byte.
Parameters
| Parameter | Required | Description |
|---|---|---|
| HTTP Method | Yes | GET (default), POST, PUT, PATCH, DELETE, OPTIONS, HEAD. |
| URL | Yes | The endpoint to call. Supports variables. |
| Headers | No | Key/value list (Authorization, Content-Type...). |
| Body | No | Request body, for methods that send one. |
| Follow redirect | No | Follow 3xx responses. Default: on. |
| Ignore SSL certificate | No | Skip certificate verification. Default: off. |
| Enable cookies | No | Keep cookies across redirects. Default: off. |
| Web access should fail | No | Invert the verdict. |
Plus the shared connection settings and DNS override. The action ships with a default assertion: status_code == 200.
Results and metrics
In the action report (result):
| Field | Description |
|---|---|
status_code | HTTP status of the response. |
body | Response body. Assert on it or extract values into variables. |
header | Response headers. |
dnslookup_duration, tcpconnection_duration, appconnect_duration, starttransfer_duration, contenttransfer_duration, total_duration | The timing waterfall: DNS, TCP, TLS, time to first byte, transfer, total. |
duration | Total execution time in seconds. |
In Analytics, each run feeds the HTTP API measurement with the full waterfall durations and duration_seconds, tagged by status, URL, HTTP method, status code, APN, antenna, and access technology.
What's next?
Last updated on