Create and update Sync Variants under a Printful Sync Product (v1 Products API)
domain: printful.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with your Printful API token (OAuth) against the v1 Products API — Sync Product/Sync Variant management is not yet available in v2.
When creating a Sync Product, include a sync_variants array; each Sync Variant must reference a Printful Catalog variant_id and one or more print files.
Attach print files either by an existing File ID from your store's file library, or by URL (files with a matching URL are reused rather than re-uploaded).
Optionally set an external_id on the Sync Product/Sync Variant so you can reference it later using an @-prefixed ID instead of Printful's internal numeric ID.
To modify an existing Sync Product's variants, resend the full sync_variants array with the IDs of every variant you want to keep — any existing variant you omit is deleted.
Known gotchas
A Sync Product supports a maximum of 100 Sync Variants — plan variant/color/size combinations accordingly.
Updating a Sync Product is destructive by omission: leaving an existing sync_variant id out of the update request deletes that variant, it isn't left untouched.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?