SoLoPrint REST API
The public SoLoPrint API is organization-scoped and built for fleet control, queue orchestration, school operations, integrations, and reporting. This page is intentionally grounded in the routes that are live in the current server so external consumers can onboard without guessing.
https://api.soloprint.appAuthorization: Bearer <api-key>2026-04-02Quickstart
Generate a key from Integrations. Keys are shown once, can expire, and should be limited to the capabilities your integration actually needs.
Call `/v1/public/version` first so your client can log the API series, active version stamp, and hosted documentation links before it starts work.
Use `/v1/org/context` or a small read endpoint during startup to confirm the key resolves into the correct organization and capability set.
Related surfaces
Every `/v1/*` response includes documentation and changelog headers so clients can surface drift in logs, dashboards, or support tooling.
Response headers
X-SoLoPrint-API-Series: v1X-SoLoPrint-API-Version: 2026-04-02X-SoLoPrint-API-Docs: https://www.soloprint.app/developers/api-docsX-SoLoPrint-API-Changelog: https://www.soloprint.app/developers/changelogCapability scopes
operations.readqueue.manageprinter.managespool.manageintegrations.manageorg.manage_usersCommon error contract
Error responses are machine-readable and typically include an `error` code plus a `details` field for operational context.
{ "error": "missing_bearer_token" }{ "error": "insufficient_permissions" }{ "error": "organization_not_found" }{ "error": "queue_item_not_assignable", "details": "..." }{ "error": "webhook_create_failed", "details": "..." }Public contract and auth bootstrap
/v1/public/version/v1/me/v1/org/context/v1/org/sso/completeOrganizations and school operations
/v1/org/users/v1/org/users/bulk/v1/platform/classes/v1/platform/user-groups/v1/platform/sso/providers/v1/platform/sso/group-mappingsFleet, queue, and materials
/v1/printers/v1/platform/printers/:printer_id/dispatch-next/v1/platform/queue/v1/platform/queue/v1/platform/queue/:queue_item_id/recompute/v1/platform/queue/:queue_item_id/assign/v1/spools/v1/spools/:spool_id/deductFiles and integrations
/v1/files/v1/files/register/v1/files/upload-from-url/v1/files/:fileId/download/v1/platform/api-keys/v1/platform/webhooks/v1/platform/webhook-deliveries/v1/platform/webhook-deliveries/:webhook_delivery_id/replayRequest examples
curl https://api.soloprint.app/v1/public/versioncurl https://api.soloprint.app/v1/printers \
-H "Authorization: Bearer <api-key>" \
-H "Accept: application/json"curl https://api.soloprint.app/v1/platform/webhooks \
-X POST \
-H "Authorization: Bearer <api-key>" \
-H "Content-Type: application/json" \
-d '{
"name": "Operations endpoint",
"endpoint_url": "https://example.com/webhooks/soloprint",
"subscriptions": ["queue_item.assigned", "spool_assignment.created"],
"max_attempts": 5,
"retry_backoff_seconds": 300
}'Key management
Create capability-scoped keys, rotate them cleanly, and audit which surfaces they can reach.
Open IntegrationsContract tracking
Pair the version endpoint with the changelog so downstream tools can flag when the hosted contract changed.
Review release notesOperational readiness
Before rotating credentials or troubleshooting delivery issues, check public platform health and recent incidents.
Open status page