Mobile Calls
Last reviewed: September 21, 2026
Use this reference for mobile-related serviceMobile calls inneed AIQto Services Workbench. Keep mobile automation logic separated from Scenario Editor UI validation unlesshave a workflowstart() requires both.call.
Recommended
start() guidance
→ Confirmvoidwhetherthe test needs a service call,Initiates a mobiledevicesession.action,orclose() → void
Stops a
ScenariomobileEditorsession.validation.Parameterize
device,platform,Forenvironment,anandideapayloadofvalues.Log request and response details without exposing tokens or user data.
Validation workflow
Identify theUX mobileendpointtestingorcapabilitiesactionseebeingSamplevalidated.DefineMobileinputScriptsparameters and expected response fields.Build the service call with reusable variables and data sources.Run a small validation and confirm response status, body, and timing.Link the service result to downstream Scenario Editor or API assertions only when needed.
Note: If an article only lists obsolete mobile APIs, consolidate it into the current Services Workbench reference.
Last updated: SeptemberJuly 21,03, 20262023
If you have any feedback on this topic, please contact us at documentation@appvance.ai.