Same data. Same auth. Three surfaces to fit how you build.
Pick the surface that matches your job. Most real integrations pair two of them - REST API to query, webhooks to react. Add the MCP server when an AI assistant joins the loop. No SDK lock-in, no proprietary protocol, no separate billing.
Three developer surfaces, one fleet
Each one solves a different shape of problem. Use one. Use all three. They share the same per-user permission model, the same data shapes, and the same account.
JSON over HTTPS with one X-API-KEY header.
Push events to any URL, Discord, Slack or Teams.
Native tool surface for Claude, ChatGPT and other AI assistants.
What developers actually build with SimplyPrint
Real patterns we see across print farms, schools, makerspaces, OEM partners and integration vendors:
- Custom job intake - a quoting portal or ERP that drops paid orders straight into the SimplyPrint queue via /queue/AddItem, with a webhook firing back when the print finishes. ShipStation, Shopify and bespoke order portals all wire up this way.
- Production dashboards - a TV-sized status board or BI dashboard that polls the API for live printer state, queue depth and daily throughput. Pair with webhooks for instant updates instead of poll loops.
- Discord, Slack and Teams pipes - paste a channel webhook URL, pick the events that matter to the team, get native messages. Zero-code shop notifications.
- AI assistants - connect Claude, ChatGPT or Gemini via MCP and let the assistant approve queue items, find low-stock spools, or summarise yesterday's print history in plain English.
- Hardware integrations - new AutoPrint hardware (plate-swappers, push-off systems, belt mods) plug in via the AutoPrint integration framework with a few gcode snippets and an Integration class.
- White-label deployments - OEM partners use the same API surface to drive a branded customer experience on top of SimplyPrint.
OAuth2 for third-party apps and platforms
Building a product that other SimplyPrint customers will connect to their account? Use OAuth2 instead of asking each customer to paste an API key. They click Connect SimplyPrint, log in on simplyprint.io, see the exact list of scopes you're requesting, and approve. You get a bearer token bound to the account they picked - no shared secrets, no copy-paste credentials, no support tickets about lost API keys.
This is the same OAuth2 flow we provision for partner integrations on platforms like Zapier, n8n, Make and Activepieces. The canonical URLs are:
- Authorize: simplyprint.io/panel/oauth2/authorize
- Token exchange: simplyprint.io/api/0/oauth2/Token
- Discovery: call /account/GetUser after exchange to find the bound account, then use /api/{companyId}/{endpoint}
Custom AutoPrint hardware integrations
Building hardware that automates print clearing - a plate-swapper, a push-off mechanism, a belt mod, a parts catcher? SimplyPrint's AutoPrint framework is the integration point. Each hardware integration registers its own Gcode template, an enum case for the method, and an Integration class that exposes marketing metadata and the MethodDefinition SimplyPrint uses to discover and drive the hardware.
Existing partners include the Chitu PlateCycler, JobOx, FarmLoop and the SimplyPrint AutoPrint device itself - all wired through the same integration framework. The hardware vendor (or SimplyPrint, on the vendor's behalf) ships a single PHP class and a Gcode snippet; the rest - method discovery, panel UI, queue handoff, on-end gcode, push-off detection - is handled by the framework. Talk to us via [email protected] if you're building hardware that should ship as a first-class AutoPrint method.
Plan access: who can use each developer surface
All three developer surfaces are part of the standard SimplyPrint plans - no separate developer seat, no per-call billing, no per-event fee. The Free, Basic, Cloud Slicer and Filament Manager plans do not expose any developer surface; everything below is gated to Pro and above.
| Feature / Limit | Free | Basic | Pro | Print Farm | Enterprise | School | Cloud Slicer | Filament Manager |
|---|---|---|---|---|---|---|---|---|
|
Basic API access
Pro and above. JSON over HTTPS, one X-API-KEY header. Read access plus light writes - printer state, queue items, jobs, filament inventory, tags and groups. 60 requests per minute on Pro, 180 on Print Farm and School, 600 on Enterprise.
|
||||||||
|
Enhanced API (full read & write)
Print Farm and above. Unlocks file uploads via /queue/AddItem, queue mutations that start prints, direct G-code send, and bulk write operations. Inherits the plan's higher rate-limit pool.
|
||||||||
|
Webhooks
Print Farm and above. Full multi-channel webhook system - regular JSON, Discord, Slack and Microsoft Teams - with 60+ events, optional HMAC signing, and per-delivery history. No per-webhook fee, no per-delivery fee, no event caps.
|
||||||||
|
MCP server for AI assistants
Pro and above. Connect Claude (claude.ai, Claude Desktop, Claude Code), ChatGPT, Gemini, Cursor and any other MCP-aware assistant to drive your fleet in natural language. OAuth-based, scope-gated, no per-call fee. The assistant's own subscription is paid to its vendor.
|
||||||||
|
Zapier, n8n, Make & Activepieces
Pro and above can connect via the official OAuth2-based pieces. Print Farm and above get full write access through them since the integrations ride the account's API tier.
|
Want to learn more about our plans?
View full pricing & feature comparisonGetting started
Pick the surface that fits your job and go:
- REST API: sign in to the panel, open account settings -> API, name a key, copy it. Then read the full reference at apidocs.simplyprint.io - including an llms.txt file and a structured api/index.json catalogue if you want to build tooling on top of the docs themselves.
- Webhooks: open the webhooks page in the panel, paste a destination URL (any URL, or a Discord / Slack / Teams channel webhook), pick the events that matter. Test deliveries are one click away. Walkthrough: all about the webhooks feature.
- MCP: paste https://simplyprint.io/api/mcp into your AI assistant's custom-connector / MCP-server settings, run through the OAuth consent screen, ask the assistant a question. Step-by-step: connect SimplyPrint to any AI assistant via MCP.
- OAuth2 partner apps: request a client via the OAuth2 Client Request Form, then point your app at the URLs above.
Frequently asked questions
Which plan do I need to use the API?
Is the API versioned?
What are the rate limits?
How do I get an API key?
API key or OAuth2 - which should I use?
API, webhooks, MCP - what's the difference?
Are there official SDKs?
Is there a sandbox or test environment?
Does my data train any AI?
Where do I get help if I'm stuck?
Step-by-step setup guides
Full client-by-client walkthroughs for every surface live in the developers section of the helpdesk - API key setup, webhook configuration for Discord / Slack / Teams, and MCP setup walkthroughs for Claude, ChatGPT and Gemini CLI.