Skip to main content
POST
/
api
/
cameras
/
{cameraId}
/
actions
/
zoom
Power zoom control
curl --request POST \
  --url http://{host}:{port}/api/cameras/{cameraId}/actions/zoom \
  --header 'Content-Type: application/json' \
  --data '
{
  "direction": "in",
  "speed": "normal"
}
'
{
  "success": true,
  "message": "<string>",
  "camera": {
    "connected": false,
    "model": "ILCE-7M4",
    "id": "D06CE05E3323"
  },
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://crsdk.app/llms.txt

Use this file to discover all available pages before exploring further.

Path Parameters

​
cameraId
string
required

Camera identifier (e.g. D10F60149B0C)

Body

application/json

Power zoom command. The server accepts two forms:

  • Direction + speed preset (ZoomDirectionalRequest): { "direction": "in" | "out", "speed": "normal" | "fast" }.
  • Signed speed (ZoomSignedSpeedRequest): { "speed": -10..+10 }. Negative = zoom out, positive = zoom in, magnitude = speed. 0 stops the zoom.

The two forms are disjoint on the speed field's JSON type, so generated SDKs may either expose them as an untagged union or surface one method per form (see x-fern-sdk-method-name on the endpoint).

​
direction
enum<string>
required
Available options:
in,
out
​
speed
enum<string>
required
Available options:
normal,
fast

Response

Zoom command executed

Generic envelope returned by most camera operations. The shape of data varies per endpoint — most operations return an empty or null data; operations that return structured data document a specific shape. SDK-generated types can treat data as an opaque map for generic endpoints.

​
success
boolean
required
​
message
string
​
camera
object

Camera info embedded in API responses

​
data
object