AWS Device Farm
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting Qahmac77 EndpointsREST
For Agents
Run mobile and web app tests on real devices and Selenium browsers in AWS, manage projects and device pools, and retrieve run, job, and artifact results.
Use for: Schedule a mobile test run on Android tablets, Upload a new APK to AWS Device Farm, List all available iPhone models in Device Farm, Create a Selenium TestGrid project for web testing
Not supported: Does not handle device emulation, beta distribution, or app store deployment — use for real-device test orchestration and Selenium browser testing only.
Jentic publishes the only available OpenAPI specification for AWS Device Farm, keeping it validated and agent-ready. AWS Device Farm lets you test mobile and web applications across real phones, tablets, and desktop browsers in the AWS cloud. The API covers the full mobile testing lifecycle — projects, device pools, uploads, runs, jobs, suites, and tests — as well as the desktop browser TestGrid for Selenium-based web testing. Use it when an agent or pipeline needs to provision device pools, kick off test runs against real hardware, and pull results without the AWS console.
Install Jentic One Beta
Connect the AWS Device Farm to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AWS Device Farm, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AWS Device Farm API.
Schedule mobile test runs against real phones and tablets with ScheduleRun and a curated DevicePool
Provision Selenium-based browser sessions on demand via CreateTestGridUrl and CreateTestGridProject
Upload application binaries and test packages with CreateUpload and track ingestion status
Curate device coverage by listing available devices, building DevicePools, and applying NetworkProfiles
Inspect run, job, suite, and test results to identify failing devices, artifacts, and test cases
Apply VPCEConfigurations and InstanceProfiles to give tests private network access to backend services
Use Cases
Patterns agents use AWS Device Farm API for, with concrete tasks.
★ Continuous Mobile Test Runs in CI
Wire Device Farm into a CI pipeline so every build of a mobile app runs against a curated pool of real Android and iOS devices. CreateUpload pushes the new APK or IPA, ScheduleRun launches the test against a DevicePool, and GetRun and ListJobs poll for completion before the pipeline reports pass or fail.
Call CreateUpload to push the new APK, ScheduleRun against a DevicePool of the top 10 Android devices, then poll GetRun until status is COMPLETED.
Selenium Browser Testing via TestGrid
Run cross-browser Selenium tests on demand by creating a TestGrid project and requesting a TestGrid URL. The framework points its WebDriver at the issued URL, executes the suite, and Device Farm records artifacts and session results that can be pulled back via GetTestGridSession and ListTestGridSessionArtifacts.
Call CreateTestGridProject, then CreateTestGridUrl with an expiresInSeconds of 3600, and supply the returned URL to the Selenium WebDriver.
Curate Device Pools for Coverage
Maintain DevicePools that reflect the customer device mix — top-selling Android phones, the latest iPhone generation, and a long-tail OS coverage pool. CreateDevicePool, UpdateDevicePool, and ListDevices let teams keep test coverage current as new devices are added to the Device Farm fleet.
Call ListDevices filtered to OS_VERSION GREATER_THAN 14, then CreateDevicePool named ios-current with those device ARNs.
Agent-Driven Mobile Test Orchestration
An AI agent connected via Jentic can react to a new build event, locate the right Device Farm project, schedule a test run, and report failures back to the team — all without bespoke AWS SDK plumbing. Jentic returns the matching Device Farm operation and schema so the agent can sequence Upload, ScheduleRun, and GetRun calls correctly.
Search Jentic for 'schedule a Device Farm run', load the ScheduleRun schema, and execute it with the projectArn, appArn, devicePoolArn, and test specification.
Key Endpoints
77 endpoints — jentic publishes the only available openapi specification for aws device farm, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateProject
Create a Device Farm project
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateUpload
Initiate an application or test upload
POST
/#X-Amz-Target=DeviceFarm_20150623.ScheduleRun
Schedule a test run against a device pool
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateDevicePool
Create a device pool
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateTestGridProject
Create a Selenium TestGrid project
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateTestGridUrl
Request a Selenium TestGrid session URL
POST
/#X-Amz-Target=DeviceFarm_20150623.StopRun
Stop a running test run
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateProject
Create a Device Farm project
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateUpload
Initiate an application or test upload
POST
/#X-Amz-Target=DeviceFarm_20150623.ScheduleRun
Schedule a test run against a device pool
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateDevicePool
Create a device pool
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateTestGridProject
Create a Selenium TestGrid project
POST
/#X-Amz-Target=DeviceFarm_20150623.CreateTestGridUrl
Request a Selenium TestGrid session URL
POST
/#X-Amz-Target=DeviceFarm_20150623.StopRun
Stop a running test run
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys for Device Farm are stored encrypted in the Jentic vault. Jentic signs each Device Farm request with SigV4 at execution time and the agent only sees scoped, short-lived access — raw access keys never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'schedule a Device Farm run' or 'create a TestGrid URL') and Jentic returns the matching Device Farm operation with its input schema, so the agent can call the right endpoint without browsing AWS documentation.
Time to first call
Direct Device Farm integration: 2-5 days for SigV4 signing, upload handling, run polling, and artifact retrieval. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AWS Device Farm API through Jentic.
Why is there no official OpenAPI spec for AWS Device Farm?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AWS Device Farm via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AWS Device Farm API use?
Device Farm uses AWS Signature Version 4 (HMAC) signing with an AWS access key ID and secret access key. Through Jentic, those credentials live encrypted in the Jentic vault and are injected into signed requests at execution time, so the agent never sees the raw secret access key.
Can I run Selenium tests on real desktop browsers with this API?
Yes. Use CreateTestGridProject and CreateTestGridUrl to provision a Selenium-compatible WebDriver endpoint. Point the Selenium framework at the returned URL and Device Farm records the session for later retrieval via GetTestGridSession.
What are the rate limits for the AWS Device Farm API?
Device Farm shares standard AWS service quotas, which are managed per account and region rather than published as fixed per-second limits in the spec. The number of concurrent runs and devices is also gated by Device Farm's per-account limits, and ThrottlingException responses should trigger backoff.
How do I schedule a mobile test run through Jentic?
Search Jentic for 'schedule a Device Farm run', load the ScheduleRun operation schema, then execute it with projectArn, appArn, devicePoolArn, and the test specification. Run pip install jentic to use the async SDK pattern.
Does this API include the test results, or just the run metadata?
Run, job, suite, and test status are returned by GetRun, GetJob, GetSuite, and GetTest. Detailed artifacts such as logs, screenshots, and video are listed via ListArtifacts, and each artifact's downloadable URL is included in the response so they can be pulled directly.
GET STARTED