Submit a print order to Cloudprinter via the Core API
domain: api.cloudprinter.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for a Cloudprinter client account and generate an API key from the CloudCore API Interface in the admin panel.
POST to https://api.cloudprinter.com/cloudcore/1.0/orders/add with your apikey, a unique order reference, one or more items, and a delivery address.
For each item, set reference, product (a valid Cloudprinter product name from the Products call), count, shipping_level (e.g. cp_postal, cp_ground, cp_saver, cp_fast), and file URLs Cloudprinter can fetch.
Send Content-Type application/json on every request; a 200/201 response confirms the order was registered.
Store the returned order reference and poll the order info endpoint, or rely on CloudSignal Webhooks, to track production and shipping progress.
Known gotchas
Every order and item reference must be unique per account/order respectively — reusing a reference id causes the request to be rejected.
Files are pulled by URL after the order is accepted, so the file URL must remain publicly reachable (ideally HTTPS with restricted access) until Cloudprinter downloads it.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?