Skip to main content
Version: 1.0.7

Device Farm API Guidance

MobileHub uses a connected Device Farm service for inventory, files, reservations, sessions, evidence, automation, and reporting. Its precise base URLs, payloads, limits, and available operations are deployment-specific.

Use the current contract​

  • Generate Appium/WebDriver configuration from Appium Config.
  • Create credentials in API Keys and CLI.
  • Use the CLI installation and API contract supplied by your current environment.
  • Treat identifiers, file references, capabilities, and limits returned by the service as authoritative.

Older endpoint examples have been removed from the current docs because they could direct automation to the wrong service or describe a retired payload.

Automation safety​

  • Put API keys in a protected secret store.
  • Verify the target organization, project, device criteria, and application before starting a session.
  • Use read-only calls to diagnose an environment before creating, terminating, or deleting resources.
  • Avoid logging authorization headers or generated configuration that contains a real key.
  • Handle rate limits and transient Device Farm outages with bounded retries.

For RabbitQA associations and events, see Test Events and RabbitQA Handoffs.