# Touch - Click

Tap a point on the Cloud Phone screen.
- **Preconditions**: the phone must be powered on and not held by another member. Supported on compatible device models only; incompatible models reject the call.
- **Coordinates**: `pos` must hold exactly two values, `[x, y]`. **They are not checked against the screen resolution** — an off-screen point is passed through to the service.
- **Completion**: synchronous. `data.status` is `finish` when the gesture completed, or `pending` when the service queued it. Some models always report `finish`. There is no endpoint to poll a `pending` gesture.
- **Retry**: no deduplication. Two calls are two taps, so a blind retry after a timeout can double-tap.
- **Note**: `duration` is accepted but ignored here; only long press reads it.

Documented business errors: `33300`, `33301`, `33401`. See [Error Codes](../Getting%20Started/error-codes.md) for what each code means. Any operation can additionally return the common codes.

Endpoint: POST /api/cloudphone/touch/click
Version: 2026-09-05

## Request fields (application/json):

  - `id` (string, required)
    Cloud Phone ID
    Example: 1558968155668507

  - `pos` (array, required)
    Tap coordinates [x, y]. The coordinate system uses the top-left corner as origin (0, 0).
    Example: [540,960]

  - `duration` (integer)
    Press duration in milliseconds (used for long press). If omitted, the default duration is used.
    Example: 2000

## Response 200:

  - `200` (unknown)
    Operation successful

## Response 200 fields (application/json):

  - `code` (integer)
    Status code, 0 means success
    Example: 0

  - `msg` (string | null)
    Response message
    Example: success

  - `data` (object)

  - `data.status` (string)
    Execution status
    Example: finish