Prusa API

Queue a print on a specific Prusa in one API call

POST a file ID, target a printer, set the position. SimplyPrint runs the print through the same queue, approval and routing logic the panel uses - so the print starts on your Prusa exactly as it would if a human pressed Print.

# Queue a print on a specific Prusa MK4 (printer id 42)
curl -X POST "https://api.simplyprint.io/{companyId}/queue/AddItem" \
  -H "X-API-KEY: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "fileId": "benchy_gcode_file_id",
    "amount": 1,
    "for_printers": "42",
    "position": "top"
  }'

Want SimplyPrint to pick the best-matching Prusa instead of a specific one? Drop the for_printers field and the queue picks an operational Prusa that has the right build volume and filament loaded.

List, inspect, pause, resume - the everyday operations

Every printer-control endpoint works the same way on a Prusa as on any other printer in your fleet. Pass the printer ID, get JSON back.

# List every printer in the account (Prusa, Bambu, anything)
curl "https://api.simplyprint.io/{companyId}/printers/Get" \
  -H "X-API-KEY: your_api_key_here"

Send any G-code your firmware accepts - useful for Prusa-specific maintenance routines, calibration sequences, or quick fixes:

# Send a one-off G-code command - home all axes on a Prusa MK4
curl -X POST "https://api.simplyprint.io/{companyId}/printers/actions/SendGcode" \
  -H "X-API-KEY: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "pid": 42, "gcode": "G28" }'

Pause or resume a print without touching the printer's LCD:

# Pause a running print on a Prusa
curl -X POST "https://api.simplyprint.io/{companyId}/printers/actions/Pause" \
  -H "X-API-KEY: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "pid": 42 }'

Why use SimplyPrint instead of Prusa Connect's API?

Prusa Connect is read-only in many views - you can monitor, but not start prints, manage queues, or send G-code remotely. SimplyPrint gives you the full write surface from one REST call. Prusa Connect is Prusa's own first-party panel and exposes its own (limited) API surface. SimplyPrint gives you a broader API for the same printers, plus things Prusa Connect doesn't cover:

SimplyPrint and Prusa Connect can co-exist; running both is fine and Prusa's own slicer and uploads keep working in parallel. Need cloud slicing too? See the PrusaSlicer Cloud integration for slicing STL to G-code from your own code before queueing.

PrusaSlicer Cloud integration

Pairs naturally with webhooks and the cloud PrusaSlicer

The Prusa API is one corner of a larger developer surface. Pair it with webhooks for push events when a Prusa finishes a print, and with our cloud PrusaSlicer if you want to slice STL files into G-code from your own code before queueing them.

See the main API page