Creatimatic LogoCreatimatic
Request beta access
Skip to Content
Creatimatic Docs
AI agents

From a design family to a reviewed POD product

Resume the seller's existing work

  1. list_ideas with a relevant query. Read get_idea for the chosen ID.
  2. Inspect the attached design family, artwork prompt, saved render data, light/dark artwork and product template. Ask the seller for missing decisions instead of inventing them.
  3. Use generate_artwork only when source artwork is needed and the idea is prepared. This is separate from rendering the final template.
  4. Use render_variations for existing variation ideas. Inspect every per-item result; partial failure is possible. This tool does not create variation ideas.
  5. If the idea already has a product, use get_product. Otherwise use create_product_from_idea after its template and finished artwork are saved. Product creation leaves publication pending and does not compose new mockups by itself.

Preserve the design family's layout, fonts, letter spacing, fitted text and colors unless the seller requests a change. The available rendering path uses existing Creatimatic workflows. Browser-native mockup composition and server design rendering are different paths; do not assume their pixels are interchangeable without visual verification.

Mockup batches

  1. Read get_product_template. Its source images and masks specify the artwork tone, placement and surface composition. Use the existing native composer in Creatimatic or a compatible client renderer. There is no new server-side mockup pixel renderer in this release.
  2. Inspect the current product gallery and enabled supplier color/size options. Use light-shirt artwork on light garments and dark-shirt artwork on dark garments, respecting the saved per-mask choice. Review contrast visually.
  3. Call begin_mockup_batch for the product. Record its ID and current base revision. A new batch supersedes prior pending batches of the same kind.
  4. Call prepare_mockup_upload for each composed PNG with the owned source template image ID, a stable slot key, name and expected byte size. It returns presignedUrl, imageUrl and imageId.
  5. PUT raw PNG bytes to presignedUrl with Content-Type: image/png. Do not send your Creatimatic agent key to storage.
  6. Call complete_mockup_upload with the batch and image ID. Verification checks that an uploaded object exists and is nonempty; it does not certify design correctness or image quality.
  7. Call apply_mockup_batch with verified imageId, imageUrl as url, templateImageId, position and name. Default replaceAll: false updates selected images. replaceAll: true intentionally replaces the whole gallery with the supplied set.
  8. Use get_mockup_batch and get_product to verify the actual saved gallery. Re-review after any artwork or gallery change.

All tool mutations need distinct idempotency keys per intended step. Image upload bytes go directly to signed storage and are not sent inside the 64 KiB API request body. The existing render lifecycle rejects stale revisions and cleans up rejected/expired staging assets according to its retention rules.

Copy and product details

Use update_product_draft for title, description, tags and price. Ground claims in the actual garment model, available colors and sizes, intended artwork and saved personalization settings. Do not claim personalization, materials, shipping times or print methods that the product cannot support.

Match the gallery to the options the buyer can select. Avoid mockups of unavailable colors or ordering instructions that claim unavailable sizes. A general manufacturer's size guide can cover additional sizes, but the listing must clearly state which sizes this product actually offers.

Seller-reviewed Etsy posting

Call prepare_publish_review and give the seller its reviewPath on their own Creatimatic origin. They sign in as the owning seller, inspect the Images and General tabs, and check Compliance and supplier options. The Publish button opens a separate review confirmation. Publish to Etsy is the final seller action.

The external API does not approve publication, queue Etsy synchronization or route the final post to a marketplace account. This boundary keeps the agent's draft work separate from the seller's posting decision.