Printify (Print on Demand)
Purpose
Use the printify CLI to manage shops, products, uploads, orders, and catalog lookups.
Tooling
Use the installed CLI directly from PATH:
printify <subcommand> [options]
Global flags:
--timeout-secs <seconds> (optional, default 30): HTTP timeout.
Core commands:
status
authorize-url
verify
set-token (reads token from stdin)
disconnect
shops
products --shop-id <id> [--product-id <id>]
create-product --shop-id <id> --json '<json>'
update-product --shop-id <id> --product-id <id> --json '<json>'
delete-product --shop-id <id> --product-id <id>
publish-product --shop-id <id> --product-id <id>
orders --shop-id <id> [--order-id <id>]
create-order --shop-id <id> --json '<json>'
upload --file <path>
blueprints [--blueprint-id <id>]
print-providers --blueprint-id <id>
variants --blueprint-id <id> --provider-id <id>
shipping --blueprint-id <id> --provider-id <id>
JSON output contract:
status: parse ok, status, connect_url, disconnect_url, and reason
authorize-url: parse ok, authorize_url, and connect_url
verify: parse ok, action, and error
set-token: parse ok, status, and reason
disconnect: parse ok, action, config_path, removed
- parse
ok, status, body, and error
- Read results retain Printify's raw timestamps and add semantic UTC and
user-local forms for record creation/update and order production,
fulfillment, delivery, or cancellation times.
Auth
First-use setup:
- Run
printify status to check connection state.
- If not connected and
connect_url is present, replace <connect_url> with the returned URL and share exactly this Markdown link: [Connect Printify](<connect_url>); do not paste the raw URL separately.
- If
connect_url is missing, run printify authorize-url and share the returned connect_url the same way.
- The user can generate a token at
https://printify.com/app/account/api.
- If the user provides a token through the CLI flow, store it only through
printify set-token; do not write auth files directly.
- Run
printify verify after setup when you need to confirm the token works.
- Never print the access token in chat output.
Operating Rules
- Always check
printify status before API calls. If not connected, guide the user through the auth setup above.
- List shops before performing shop-specific operations to get the correct
shop_id.
- Confirm with the user before creating, updating, or publishing products. Product deletion may proceed from a clear, unambiguous request without an additional confirmation.
- Confirm with the user before creating orders (orders may trigger charges).
- When browsing the catalog, start with
blueprints then drill into print-providers and variants.
- On HTTP 401, tell the user their token may be expired and to generate a new one at
https://printify.com/app/account/api.
1---2name: "printify"3description: "Use Printify to browse catalog data, manage shops and products, and review or create orders."4icon: "printify"5metadata:6 source: https://skillmd.com/skills/win4r/printify7 includeInPrompt: false8---910# Printify (Print on Demand)1112## Purpose13Use the `printify` CLI to manage shops, products, uploads, orders, and catalog lookups.1415## Tooling16Use the installed CLI directly from `PATH`:1718```sh19printify <subcommand> [options]20```2122Global flags:23- `--timeout-secs <seconds>` (optional, default 30): HTTP timeout.2425Core commands:26- `status`27- `authorize-url`28- `verify`29- `set-token` (reads token from stdin)30- `disconnect`31- `shops`32- `products --shop-id <id> [--product-id <id>]`33- `create-product --shop-id <id> --json '<json>'`34- `update-product --shop-id <id> --product-id <id> --json '<json>'`35- `delete-product --shop-id <id> --product-id <id>`36- `publish-product --shop-id <id> --product-id <id>`37- `orders --shop-id <id> [--order-id <id>]`38- `create-order --shop-id <id> --json '<json>'`39- `upload --file <path>`40- `blueprints [--blueprint-id <id>]`41- `print-providers --blueprint-id <id>`42- `variants --blueprint-id <id> --provider-id <id>`43- `shipping --blueprint-id <id> --provider-id <id>`4445JSON output contract:46- `status`: parse `ok`, `status`, `connect_url`, `disconnect_url`, and `reason`47- `authorize-url`: parse `ok`, `authorize_url`, and `connect_url`48- `verify`: parse `ok`, `action`, and `error`49- `set-token`: parse `ok`, `status`, and `reason`50- `disconnect`: parse `ok`, `action`, `config_path`, `removed`51- parse `ok`, `status`, `body`, and `error`52- Read results retain Printify's raw timestamps and add semantic UTC and53 user-local forms for record creation/update and order production,54 fulfillment, delivery, or cancellation times.5556## Auth57First-use setup:581. Run `printify status` to check connection state.592. If not connected and `connect_url` is present, replace `<connect_url>` with the returned URL and share exactly this Markdown link: `[Connect Printify](<connect_url>)`; do not paste the raw URL separately.603. If `connect_url` is missing, run `printify authorize-url` and share the returned `connect_url` the same way.614. The user can generate a token at `https://printify.com/app/account/api`.625. If the user provides a token through the CLI flow, store it only through `printify set-token`; do not write auth files directly.636. Run `printify verify` after setup when you need to confirm the token works.647. Never print the access token in chat output.6566## Operating Rules671. Always check `printify status` before API calls. If not connected, guide the user through the auth setup above.682. List shops before performing shop-specific operations to get the correct `shop_id`.693. Confirm with the user before creating, updating, or publishing products. Product deletion may proceed from a clear, unambiguous request without an additional confirmation.704. Confirm with the user before creating orders (orders may trigger charges).715. When browsing the catalog, start with `blueprints` then drill into `print-providers` and `variants`.726. On HTTP 401, tell the user their token may be expired and to generate a new one at `https://printify.com/app/account/api`.