Migrating from Prusa Connect

The Prusa Connect camera paths still work. This page maps them to the current paths and bodies.

Path mapping

Prusa Connect path	Current path
https://connect.prusa3d.com/c/info	https://camera-service.prusa3d.com/v1/camera-info
https://connect.prusa3d.com/c/snapshot	https://camera-service.prusa3d.com/v1/snapshot

Still supported

The Prusa Connect paths keep accepting the Prusa Connect request format. Use the current paths in new code.

Camera info body mapping

Prusa Connect field	Current field
config.name	config.name
config.path	config.path
config.driver	config.driver
config.rotation	config.rotation, the physical rotation as mounted
config.trigger_scheme	config.trigger_scheme, now one of the trigger schemes
config.resolution	config.resolution
config.network_info	config.network_info
config.manufacturer, config.model	device.manufacturer, device.model
type	device.type, required
firmware_version, config.firmware	device.firmware_version, required
hardware_version, config.hardware	device.hardware_version, required
protobuf_version, config.protobuf	device.protobuf_version
features	features
capabilities, options, sort_order	Removed
any other config key	Removed: unknown keys are rejected

The response has the same shape as the request. The Prusa Connect fields id, token, origin, registered, team_id and printer_uuid are gone.

Differences from the old Prusa Connect camera docs

• Every request needs a User-Agent header.
• Errors use one JSON shape, and invalid bodies get 422 with details. See errors.
• Validation is strict: unknown keys are rejected, and device.type must be a real camera type (no OTHER or UNKNOWN).
• The maximum snapshot size is 1 MB, not 16 MB.
• Content-Length is required on snapshot uploads, so chunked transfer is rejected with 411.
• Snapshot uploads are limited to 6 uploads per minute per camera. Uploading every 10, 30 or 60 seconds stays within the limit.
• The first authenticated call must arrive within 15 minutes of creating the camera, see authentication.

Rules for AI readers

• Generate new code against the current paths in the table, never the Prusa Connect paths.
• Always send device with type, firmware_version and hardware_version.
• Send only the documented keys.