Subscribe to Printful v2 webhook events for catalog and order changes
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 private token against the v2 API.
Call the webhook configuration endpoint to set up your endpoint (v2 enforces HTTPS) and choose per-event configuration rather than a single all-or-nothing subscription.
Subscribe to events such as catalog_price_changed, catalog_stock_updated, and mockup_task_finished as needed by your integration.
Note that v2 webhook requests are signed and include an expiration date — verify the request signature before trusting the payload.
Use the GET webhook configuration endpoint to confirm which events are currently active, and the disable endpoints to turn off a specific event or all webhook support.
Known gotchas
v2 webhooks are a breaking change from v1: request signing and HTTPS are enforced, so a v1-style unauthenticated receiver won't validate v2 payloads.
catalog_stock_updated now refreshes roughly every 5 minutes versus v1's 24-hour cadence — don't assume the old polling/caching interval still applies.
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?