Printify

Printify

This connector talks to the Printify REST API v1 (https://api.printify.com/v1). Printify prints and ships products on demand; the merchant designs a product in Printify and Printify publishes it to a sales channel such as Etsy, Shopify, WooCommerce or a custom API store.

Setup

1. In Printify open My Profile → Connections and click Generate under Personal Access Tokens.
2. Pick the access scopes. For everything this connector does: shops.read, catalog.read, print_providers.read, products.read, products.write, orders.read, orders.write, uploads.read, uploads.write, webhooks.read. A read-only setup only needs the *.read scopes.
3. Copy the token (it is shown once) into PRINTIFY_API_TOKEN. Tokens expire after one year; generate a new one then.

The token is sent as Authorization: Bearer <token>. Printify also requires a User-Agent header on every request; the connector sends one.

Start here

Call printify_list_shops first. Every product, order and webhook belongs to a shop, and the shop id (a number) is the shop_id of all shop tools. The sales_channel field tells where the shop publishes (for example etsy, shopify, custom_integration, or disconnected).

Printify and Etsy

An Etsy shop connected to Printify appears in printify_list_shops with sales_channel etsy. Products are created and edited in Printify; printify_publish_product pushes them to the Etsy listing (title, description, images, variants, tags and, for Etsy, the shipping profile). Etsy orders for Printify products arrive automatically and show up in printify_list_orders; there is no need to create them with printify_create_order. Use the Etsy connector for listing statistics, reviews and buyer messages, and this one for production, costs and fulfillment. Edit a published product in Printify and publish again rather than editing the Etsy listing directly, or the two drift apart.

Building a product

1. printify_list_blueprints to find the base product (a blueprint, for example a t-shirt model).
2. printify_list_blueprint_print_providers for who can print it, then printify_list_variants for sizes, colours and print area placeholders, and printify_get_shipping for shipping costs.
3. printify_upload_image with a public image URL; keep the returned image id.
4. printify_create_product with blueprint, print provider, variants (price in cents) and print areas referencing the image id.
5. printify_publish_product to send it to the sales channel.

Ids, money and pagination

• Shop ids and catalog ids (blueprint, print provider, variant) are integers; product, order, upload and webhook ids are 24-character hex strings.
• Prices and costs are integers in cents of the shop currency (2499 = 24.99).
• Lists of products, orders and uploads are paged: page starts at 1; limit is at most 50 for products, 10 for orders and 100 for uploads. The answer carries current_page, last_page and total.

Rate limits

600 requests per minute per account, and 100 per minute for catalog endpoints. Publishing is limited to 200 calls per 30 minutes. Printify asks that errors stay below 5% of all requests, so look ids up before guessing them.

Pitfalls

• printify_send_order_to_production charges the merchant's Printify balance or card. printify_cancel_order only works while the order is on-hold or payment-not-received.
• printify_publish_product does nothing visible on a shop with no sales channel; on a custom API store it only fires the publish event.
• Variants that are out of stock are hidden from printify_list_variants unless show_out_of_stock is 1.