Smartphone Test Farm
Control and manages real Smartphone devices from browser and restful apis
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Control and manages real Smartphone devices from browser and restful apis
Endpoints 10
user
- GETUser Profile
/userThe User Profile endpoint returns information about current authorized user - GETAccess Tokens
/user/accessTokensThe Access Tokens endpoints returns titles of all the valid access tokens - GETUser Devices
/user/devices?fields=stringThe User Devices endpoint returns device list owner by current authorized user - POSTAdd a device to a user
/user/devicesThe User Devices endpoint will request stf server for a new device. - GETUser Device
/user/devices/:serial?fields=stringThe devices enpoint return information about device owned by user - DELETEDelete User Device
/user/devices/:serialThe User Devices endpoint will request for device release from stf server. It will return request accepted if device is being used by current user - POSTRemote Connect
/user/devices/:serial/remoteConnectThe device connect endpoint will request stf server to connect remotely - DELETERemote Disconnect
/user/devices/:serial/remoteConnectThe device connect endpoint will request stf server to disconnect remotely
devices
- GETDevice List
/devices?fields=stringThe devices endpoint return list of all the STF devices including Disconnected and Offline - GETDevice Information
/devices/:serial?fields=stringThe device enpoint return information about a single device
API details
- Base URL
https://openstf.local/api/v1- Authentication
- An API key in the authorization header
- Operations
- 10 operations on 8 pathsGET 6POST 2DELETE 2
- Main resources
- user 8devices 2
- Response formats
application/json- Description format
- Swagger 2.0, API version
2.3.0 - Links
- OpenAPI document · Support
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the Smartphone Test Farm in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Smartphone Test Farm collection, without the publisher's secrets.
- Add your credentialsThis API uses an API key in the authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “User Profile” (GET /user), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Smartphone Test Farm?
Control and manages real Smartphone devices from browser and restful apis It is listed under Communication and has 10 endpoints.
Who publishes the Smartphone Test Farm?
It is listed from Openstf's public API description (an OpenAPI document), not published by Openstf on Swastik Codes. Anyone who controls openstf.io can claim the profile by adding a DNS TXT record.
What is the base URL of the Smartphone Test Farm?
Requests go to https://openstf.local/api/v1. Endpoint paths are added to this base URL.
How do I authenticate with the Smartphone Test Farm?
With an API key in the authorization header.
How many endpoints does the Smartphone Test Farm have?
10 operations on 8 paths (6 GET, 2 POST, 2 DELETE). The largest groups are user, devices.
Is forking the Smartphone Test Farm free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.