Printify MCP by usefulapi

Get a shipping price quote for a set of line items to a destination address. Non-destructive — it only prices, it does NOT place an order. `line_items` is an array where each item is one of {product_id, variant_id, quantity}, {print_provider_id, blueprint_id, variant_id, quantity}, or {sku, quantity}. `address_to` is the destination (first_name, last_name, email, phone, country, region, address1, address2, city, zip, company). Printify REST: POST /v1/shops/{shop_id}/orders/shipping.json.

Preview or copy selected products or a complete catalog between two Printify shops in the same account. Preserves title, description, blueprint/provider, variant IDs/prices/enabled flags, artwork IDs and print-area transforms. Preserves canvas side printing and image pattern rotation. This initial workflow does not copy tags, SKUs, channel IDs, publication state or generated mockups. Products with text/personalization layers are explicitly refused because their creation fields are read-only. Preview by default. confirm:true starts/resumes a durable bounded job; save job_id and keep calling with that job_id and confirm:true until complete. Duplicate prevention remembers copies made by this connector, including across restarts/jobs; pre-existing copies made elsewhere are not detected. An uncertain create is never automatically retried: inspect the target and use printify_resolve_copy. Do not change the source catalog during an all-products run. Requires shops.read/products.read/products.write. Confirmed copying requires the hosted connector's durable coordinator.

Read a durable product-copy job's progress, target mappings, failures and uncertain writes. Verifies that the current token can access both shops. Does not create or retry products.

WRITE: preview an order of existing enabled product variants in an API/custom-integration store. Set this exact store to Manual approval in Printify BEFORE confirmation, then pass manual_approval_confirmed:true, confirm:true and the approved preview_hash. The API cannot verify Manual approval; auto-approval can otherwise cause production/charges. Persistent operation_id prevents automatic duplicate creation. Does not submit production or send shipping notifications.

WRITE: preview an order/shipment topic and HTTPS receiver; confirm with preview_hash to register it. Uses the signing secret configured securely on the connection, never a tool argument or result. Shares event data with that receiver. Verify X-Pfy-Signature at your receiver; API acceptance is not proof of signature delivery. Duplicate/uncertain attempts are not blindly replayed.

WRITE: preview a shop's selected webhook, check expected_host against its destination, then confirm with preview_hash to delete only that webhook. Uses Printify's required host query safeguard and persistent operation deduplication.

Get a single catalog blueprint's details. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}.json.

Get a single order's full details, including `shipments` (carrier + tracking numbers). Printify REST: GET /v1/shops/{shop_id}/orders/{order_id}.json.

List the print providers that can produce a given blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers.json.

Get a single product's full details (variants, images, print areas, publish status). Printify REST: GET /v1/shops/{shop_id}/products/{product_id}.json.

List the variants (sizes, colors) a print provider offers for a blueprint. Printify REST: GET /v1/catalog/blueprints/{blueprint_id}/print_providers/{print_provider_id}/variants.json.

List all blueprints (product types, e.g. 'Unisex T-Shirt') available in the Printify catalog. Printify REST: GET /v1/catalog/blueprints.json.

List orders in a shop (paginated), optionally filtered by status or SKU. Printify REST: GET /v1/shops/{shop_id}/orders.json.

List all print providers in the Printify catalog. Printify REST: GET /v1/catalog/print_providers.json.

List products in a shop (paginated). Printify REST: GET /v1/shops/{shop_id}/products.json.

List all shops connected to the Printify account. This is the entry point — each shop's `id` is required by the product, order and webhook tools. Printify REST: GET /v1/shops.json.

List images uploaded to the account's media library (paginated). Printify REST: GET /v1/uploads.json.

List the webhooks configured for a shop. Printify REST: GET /v1/shops/{shop_id}/webhooks.json.

Publish a product to the shop's connected sales channel (e.g. Shopify, Etsy). STATE-CHANGING: this locks the product and pushes the selected fields to the external store. The body is an object of booleans controlling which fields are published; all default to true. Printify REST: POST /v1/shops/{shop_id}/products/{product_id}/publish.json.

Resolve one failed or uncertain source product in a durable copy job. Provide an existing target_product_id to verify the exact supported fields against the checkpoint and record it as copied. Or set verified_not_created:true only after checking the target shop manually; this allows one future retry through printify_copy_products. Requires confirm:true, never creates/publishes/deletes anything itself. An ambiguous write must never be blindly retried.

WRITE: separately preview and approve production of an existing order, including its destination and fulfillment costs. Can charge your linked Printify payment method. Requires production_charge_approved:true, confirm:true and preview_hash; use the same operation_id for retries. Uncertain submissions are never replayed.

WRITE: preview integer-cent retail price changes on selected variants. Confirm with preview_hash to update Printify, preserving all other variants, flags, SKUs and defaults; verify readback. Does not publish to an external sales channel. Reuse operation_id rather than blindly repeating an uncertain update.

Read the persistent state and known resource IDs for an operation on this connection in a shop authorized by the current token. Does not create, submit, update or delete anything. Reconcile an uncertain attempt before doing further writes or rotating the token; operation history is scoped to the original connection identity.