Skip to main content
POST
JavaScript
With humanize: true, the gesture is humanized: start and end points shift randomly (up to ±5 and ±15 pixels), the duration gets ±10% jitter, and supported devices trace a curved path with micro-jitter instead of a straight line. Devices with human-like input support inject the whole gesture with human motor timing instead. A humanized swipe covering less than ~5 pixels is treated as a long press with slight drift. holdMs cannot be combined with humanize; that combination is rejected with 422 SWIPE_HOLD_HUMANIZE_CONFLICT.

Authorizations

Authorization
string
header
required

Bearer token via Authorization header

Headers

X-Device-Display-ID
integer<int64>
default:0
Required range: x >= 0

Path Parameters

deviceId
string
required

Body

application/json
duration
integer<int64>
required

Swipe duration in milliseconds

Required range: x >= 10
endX
integer<int64>
required
endY
integer<int64>
required
startX
integer<int64>
required
startY
integer<int64>
required
holdMs
integer<int64>
default:0

Keep the finger at the end point for holdMs and suppress fling before lifting, so content moves by about the finger travel. Supported on Android cloud phones.

Required range: 0 <= x <= 5000
humanize
boolean

Request human-like input where supported by the device. Defaults to false.

Response

No Content