Skip to main content

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.

start() guidance

→
  • Confirmvoid whether

    the test needs a service call,Initiates a mobile devicesession. action,

    or

    close() → void

     Stops a Scenariomobile Editorsession. validation.

  • Parameterize

    device,

    platform,For environment,an andidea payloadof values.

  • Log request and response details without exposing tokens or user data.

Validation workflow

  1. Identify theUX mobile endpointtesting orcapabilities actionsee beingSample validated.
  2. DefineMobile inputScripts parameters and expected response fields.
  3. Build the service call with reusable variables and data sources.
  4. Run a small validation and confirm response status, body, and timing.
  5. 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.