How phones work in the API
Every phone connected through the TapKit Mac app becomes available via the API. Each phone has a uniquephone_id that you use to target phone-specific endpoints.
If you only have one phone connected, most endpoints auto-select it — you don’t need to specify a phone_id.
Endpoint categories
Phone endpoints are grouped by what they do:Device management
Inspection
Inspection endpoints read state or data from the connected phone through the Mac app. They do not press buttons, launch apps, or send touch input.Touch gestures
Device commands
Apps and automation
Coordinate system
All touch actions use pixel coordinates that map 1:1 with screenshot pixels. Screenshots are scaled so the longest edge is 1344px. The API handles native-to-scaled coordinate conversion transparently. For example, if a screenshot shows a button at position (300, 672), you send{"x": 300, "y": 672} to the tap endpoint.
Selector-based actions
Many touch actions also support a selector variant (e.g.,tap-select, drag-select) that lets you target elements by description rather than coordinates. This is useful when you know what you want to tap but not exactly where it is.
See the individual endpoint pages for details on selector parameters.