Skip to main content
POST
Press a button on the camera body

Path Parameters

cameraId
string
required

Camera identifier (e.g. D10F60149B0C)

Body

application/json
button
enum<string>
required

Which button to press. Not every body accepts every name — a 400 response lists what the connected camera reports as operable.

Available options:
up,
down,
left,
right,
enter,
menu,
multi-selector-up,
multi-selector-down,
multi-selector-left,
multi-selector-right,
multi-selector-enter,
multi-selector-right-up,
multi-selector-right-down,
multi-selector-left-up,
multi-selector-left-down,
fn,
playback,
delete,
mode,
c1,
c2,
c3,
c4,
c5,
c6,
c7,
movie,
ael,
af-on,
home,
clips,
slot-select,
display,
cancel-back,
thumbnail
action
enum<string>

down to hold and up to release. Omit (or send press) for a full down-then-up. An up is always accepted so a held key can be released.

Available options:
press,
down,
up

Response

Button press sent

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