If you run a Printify catalog with real sales and you are tired of clicking through the Product Creator for every new SKU, you have probably searched for a mockup generator API hoping to script the whole thing. The honest answer is more specific than the blog posts suggest. This piece covers what the API does return, where the limits bite, and how to think about automating a real catalog build-out.
Does Printify have a mockup generator API?
Not in the way the phrase implies. Printify's free Mockup Generator is a web tool inside the dashboard, and it is excellent — unlimited, watermark-free mockups across more than two thousand products, with flat lays, lifestyle scenes, close-ups, and multi-angle views. But that tool is not exposed as a public "give me a mockup" endpoint.
What Printify exposes instead is a catalog-and-product API. You create a product by choosing a blueprint, a print provider, and placing your artwork, and Printify generates the mockup renderings as part of that product. The images are the output of product creation, not a separate service you call.
This matters for how you architect any automation. You are not sending Printify a PSD and a blank and getting a picture back. You are creating real products in your account, and the mockups ride along with them.
How mockups actually come back from the Printify API
The product-first workflow
When you call POST /v1/shops/{shop_id}/products.json to create a product, Printify renders the mockups for that blueprint and provider, then returns them inside the product object's images array. Each image carries a mockup_id, a src URL, the variant_ids it applies to, a position (front, back, and so on), and flags like is_default and is_selected_for_publishing, as documented in the Printify API reference.
Those image values are read-only. You cannot POST a new mockup rendering directly; you change the design, variants, or provider on the product, and Printify re-renders. The src URLs are hosted images you can pull into your own systems, ad tools, or listing drafts.
That is the real automation surface. Create the product, read back the mockup URLs, and route them wherever you need them.
The mockup-selection endpoint
The one piece that behaves like a true "mockup control" API is the selection endpoint. A GET /v1/shops/{shop_id}/products/{product_id}/mockup-selection.json returns the available mockups, and a PATCH to the same path sets which ones publish, per the API docs.
This is how you script the part humans find tedious: picking the right three or four mockups per product and making sure the lifestyle shot leads instead of the default flat lay. Set the selection programmatically, then publish, and the storefront listing shows exactly the images you chose.
For an established store, that selection step is the conversion lever. The default rendering is table stakes; a consistent mockup style across the catalog is what makes a store look like a brand instead of a Printify template.
What the rate limits mean for a catalog build
Automation lives and dies by throughput, so read the limits before you write a loop. Printify's API allows six hundred requests per minute globally per integration, with a tighter one hundred requests per minute on catalog endpoints, and a separate cap of two hundred publish requests per thirty minutes, according to the Printify API documentation. Exceeding any of these returns a 429 Too Many Requests response.
The publish cap is the one that shapes a big catalog drop. Two hundred publishes per thirty minutes works out to roughly four hundred products per hour if you keep the pipeline full. The docs also note that errors must stay under five percent of total requests, so sloppy retry logic can get you throttled on its own.
For most operating stores this is plenty — you are not publishing thousands of SKUs an hour. But if you are migrating a catalog or running a seasonal refresh, you plan the batch around the thirty-minute publish window rather than firing everything at once.
A worked example: automating a catalog refresh
Say you run a store doing 340 orders a month at a $31 average order value, and you want to ship 60 new designs for the holiday season. Each design goes on four blueprints — a tee, a hoodie, a mug, and a tote — so that is 240 new products to create, mockup, and publish.
Doing that by hand in the Product Creator at even five minutes per product is 1,200 minutes, or 20 hours of clicking. Scripted against the Product API, the creation calls are fast; the publish step is the throttle. At 200 publishes per thirty minutes, 240 products clear in about 36 minutes of publish time plus creation overhead.
Now the part the mockup articles always skip: the money. Because Printify shows each provider's base cost before the first sale, you know your margin the moment you pick the provider. If your tee sells for $26.99 against an $11.40 base cost and roughly $4.75 shipping, that is 26.99 − 11.40 − 4.75 = $10.84 gross per order before ad spend and platform fees. Multiply that across 240 live products and the question is not "can I make mockups fast" but "which of these 240 actually clear a profit after Meta takes its cut." The mockups are the easy part.
When the API is not the right tool
If your goal is rendering your own artwork on products Printify does not stock, or on custom PSD templates, the Printify API will not help — it only renders its own catalog blanks. That is the gap dedicated mockup services fill, and it is a legitimate reason to look elsewhere for pure marketing imagery.
But if your products live on Printify anyway, routing around the API to a third-party mockup tool usually adds a sync problem instead of removing one. The mockups that publish to your store are the ones Printify generated; a prettier external render has to be manually swapped in on the storefront, and a careless republish from Printify reverts it. If you want the deeper mechanics of that republish trap and the selective-publishing safeguard, the Printify operations guide walks through it.
Most operators do not actually want to write and maintain this code. They want the catalog built, the right mockups chosen, and the products live — without becoming a part-time API engineer.
Where this fits in your Printify operation
The product build-out is exactly the repetitive work worth delegating. PodVector AI's Victor is an AI employee for POD merchants, and on Printify he creates and publishes products, selects the mockups, approves or cancels orders, and switches print providers when a provider's costs or stock turn against you. He also computes the true per-order profit on each SKU, so you learn which new designs earn their place instead of just which ones rendered nicely.
Because Victor sees every order, every ad dollar, and every supplier cost together, he can tell you the real margin on that holiday tee before you scale spend behind it. He works across Shopify, Meta Ads, Google Ads, Printful, Gelato, and Klaviyo too, so the catalog you publish and the campaigns that sell it stay connected. If you are wiring Printify into your storefront, the step-by-step on how to add products from Printify to Shopify pairs well with this, as does the setup walkthrough for adding Printify to Shopify.
You can put Victor on your Printify catalog and let the product-and-mockup grind run while you work on the designs that actually sell. For a sense of what a niche Printify catalog looks like in practice, the breakdown of Roastify's coffee product line is a useful reference.
FAQs
Can I generate a mockup from the Printify API without creating a product?
No. Mockups are produced as part of product creation, and the resulting images come back as read-only URLs on the product object, per the Printify API docs. There is no endpoint that takes raw artwork plus a blank and returns a standalone render; you create the product, then read its mockups.
How do I control which mockups publish to my store?
Use the mockup-selection endpoint. A GET on /products/{product_id}/mockup-selection.json lists the available mockups and a PATCH sets which ones publish, as described in the Printify API reference. That lets you lead with a lifestyle shot instead of the default flat lay across your whole catalog.
What are the Printify API rate limits for a big catalog drop?
The API allows six hundred requests per minute globally, one hundred per minute on catalog endpoints, and two hundred publish requests per thirty minutes per integration, with a 429 when you exceed them, according to the Printify documentation. The publish cap is the real throttle for large batches, so sequence your drop around the thirty-minute window.
Is the Printify Mockup Generator the same as the API?
No. The Mockup Generator is the free web tool in the dashboard — unlimited, watermark-free images across more than two thousand products, with AI scene generation as a Premium perk. The API is a separate catalog-and-product interface that happens to return the generated mockups; the two are related but not the same thing.
Can I get mockups for products Printify does not stock?
Not through Printify. Its rendering only covers its own catalog blanks, so custom PSDs or products it does not carry are out of scope. If your products live on Printify anyway, the native mockups are usually the practical choice; the complexity of syncing an external render back onto the listing rarely pays off.
Should I build the automation myself or delegate it?
If you enjoy maintaining API code and retry logic, the endpoints are there. If you would rather the catalog just get built and priced for profit, Victor creates and publishes the products, selects the mockups, and tells you the true per-order margin — so you spend your time on designs and offers, not on loops and 429 errors.