[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Printify API and MCP server

> Printify has a full public REST API, version 1, for shops, catalog, products, orders, uploads and webhooks, but no official MCP server (checked 17 Oct 2026). You authenticate with a personal access token or an approved OAuth app, and you build the agent tool layer yourself.

Print on demand platform: you design products, Printify prints and ships them through print providers, and your sales channel store sells them.

## What is the Printify API?

Cotlet's Printify API exposes 13 endpoints for your own Printify account: list shops, list blueprints, get blueprint variants, list products, get product, list orders, get order, upload image, create product, update product, publish product, send order to production and cancel order. The list_shops endpoint returns shops connected to your Printify account, with ID, title and sales channel. Each endpoint takes simple JSON inputs like shop_id, product_id or order_id and works both as an operation of the printify_read or printify_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 13 (7 read, 6 write)
- **Updated:** 2026-10-22

Printify has a full public REST API, version 1, for shops, catalog, products, orders, uploads and webhooks, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Printify with 13 endpoints (7 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Printify have an official API?

Printify has a full public REST API, version 1, for shops, catalog, products, orders, uploads and webhooks, but no official MCP server (checked 17 Oct 2026). You authenticate with a personal access token or an approved OAuth app, and you build the agent tool layer yourself.

| Task | Printify official | Cotlet |
|---|---|---|
| List shops, products and orders | Yes: Public API v1; orders come 10 per page at most | Yes |
| Create a product from a design | Yes: Public API v1; you pick blueprint, print provider and variants yourself | Yes |
| Upload artwork | Yes: Public API v1, by URL or base64; Printify recommends URL for files over 5 MB | Yes |
| Change variant prices | Yes: Public API v1; prices are integers in cents | Yes |
| Publish a product to the shop | Yes: Public API v1; 200 requests per 30 minutes | Yes |
| Send an order to production | Yes: Public API v1; needed only when order approval is manual | Yes |
| Cancel an order | Partly: Public API v1 cancels unpaid orders only | Yes |
| Check order status and shipments | Yes: Public API v1; webhooks cover shipment events | Yes |

Sources: [Printify developers: API reference](https://developers.printify.com/), [Printify Help: How can I edit an existing product?](https://help.printify.com/hc/en-us/articles/4483630354961-How-can-I-edit-an-existing-product), [Printify Help: How can I update my retail prices?](https://help.printify.com/hc/en-us/articles/4483625628305-How-can-I-update-my-retail-prices)

## For AI agents

```text
Printify has a full public REST API, version 1, for shops, catalog, products, orders, uploads and webhooks, but no official MCP server (checked 17 Oct 2026). You authenticate with a personal access token or an approved OAuth app, and you build the agent tool layer yourself.
Cotlet provides a hosted MCP server and REST API for Printify: 13 tools (7 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=printify, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    printify_read, printify_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/printify, each operation at its own route, e.g. PATCH /api/v1/printify/shops/{shop_id}/products/{product_id}
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_shops, list_blueprints, get_blueprint_variants, list_products, get_product, list_orders, get_order, upload_image, create_product, update_product, publish_product, send_order_to_production, cancel_order
Confirm      publish_product, send_order_to_production, cancel_order (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/printify-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=printify, requests Printify in the Cotlet console and creates an API key there.
2. The user signs in to Printify once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Printify for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Printify server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Printify MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Printify in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Printify only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Printify login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Printify's terms; Cotlet is not affiliated with Printify.
```

## What can an AI agent do in Printify?

Cotlet is best for Printify sellers who are not developers and want their AI agent to create products, publish them and watch orders without running or fixing a server.

- **[Create products from designs](https://cotlet.dev/integrations/printify-api-mcp-server/create-products-from-designs.md)**: "Upload the three PNG files from this folder URL to my Printify media library, then create a draft unisex t-shirt for each one in sizes S to XL, priced at $24.99. Do not publish anything." → `upload_image`, `list_blueprints`, `get_blueprint_variants`, `create_product`
- **[Publish products to your shop](https://cotlet.dev/integrations/printify-api-mcp-server/publish-products-to-shop.md)**: "List my unpublished Printify products in shop 8123456 and publish the ones tagged "ready". Wait if more than 20 are queued." → `list_products`, `get_product`, `publish_product`
- **[Check stuck Printify orders](https://cotlet.dev/integrations/printify-api-mcp-server/check-stuck-orders.md)** (runs: daily): "Every morning, list my Printify orders with status has-issues, on-hold or payment-not-received, say why each one is stuck and tell me which I can fix." → `list_orders`, `get_order`
- **Update variant prices across products**: "Raise the price of every enabled variant in my tees by $2, but only in products tagged "summer", and show me the old and new price first." → `list_products`, `get_product`, `update_product`, `publish_product`
- **Approve orders by your own rule** (runs: daily): "With manual approval on, send to production every Printify order from the last day that has a valid address and is not a test order. List the rest for me." → `list_orders`, `get_order`, `send_order_to_production`

## Can Printify automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Printify connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to check stuck printify orders, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/printify/shops/{shop_id}/orders. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/printify/shops/{shop_id}/orders with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Printify.

### list_shops

Shops connected to your Printify account, with ID, title and sales channel. Access: read. REST: `GET /api/v1/printify/shops`. MCP: `printify_read → list_shops`.

No parameters.

Returns every shop in your Printify account. A shop that lost its sales channel shows the channel as disconnected. Use the shop_id from each item in the other tools.

Example response:

```json
{
  "shops": [
    {
      "shop_id": 8123456,
      "title": "Night Owl Store",
      "sales_channel": "etsy"
    },
    {
      "shop_id": 8123499,
      "title": "Test shop",
      "sales_channel": "disconnected"
    }
  ]
}
```

### list_blueprints

Product types in the Printify catalog, such as t-shirts and mugs, with brand and model. Access: read. REST: `GET /api/v1/printify/blueprints`. MCP: `printify_read → list_blueprints`.

No parameters.

Returns the catalog blueprints, the product types you build from. Use blueprint_id with get_blueprint_variants to see which print providers make it and which variants they offer.

Example response:

```json
{
  "blueprints": [
    {
      "blueprint_id": 384,
      "title": "Unisex Heavy Cotton Tee",
      "brand": "Gildan",
      "model": "5000"
    },
    {
      "blueprint_id": 68,
      "title": "Accent Coffee Mug, 11oz",
      "brand": "Generic brand",
      "model": "Mug"
    }
  ]
}
```

### get_blueprint_variants

Variants one print provider offers for a blueprint, with size, color and print area size. Access: read. REST: `GET /api/v1/printify/print-providers/{print_provider_id}/blueprints/{blueprint_id}/variants`. MCP: `printify_read → get_blueprint_variants`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `blueprint_id` | integer | yes | Blueprint ID from list_blueprints. |
| `print_provider_id` | integer | yes | Print provider ID that makes the blueprint. |
| `include_out_of_stock` | boolean | no | true lists out of stock variants too. Default: false. |

Returns the variants of one blueprint at one print provider, in stock only by default. Each variant has its ID, options such as color and size, and the print areas in pixels. Set include_out_of_stock to see all of them. Catalog requests are limited to 100 per minute per account.

Example response:

```json
{
  "blueprint_id": 384,
  "print_provider_id": 29,
  "variants": [
    {
      "variant_id": 45740,
      "title": "Black / S",
      "options": {
        "color": "Black",
        "size": "S"
      },
      "print_area": {
        "position": "front",
        "width": 3153,
        "height": 3995
      }
    },
    {
      "variant_id": 45742,
      "title": "Black / L",
      "options": {
        "color": "Black",
        "size": "L"
      },
      "print_area": {
        "position": "front",
        "width": 3153,
        "height": 3995
      }
    }
  ]
}
```

### list_products

Products in a shop with title, tags, visibility and whether a publish is running. Access: read. REST: `GET /api/v1/printify/shops/{shop_id}/products`. MCP: `printify_read → list_products`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `tag` | string | no | Only products with this tag. |
| `limit` | integer | no | Products per page. Default: 10. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |

Lists the products of one shop, with title, tags, whether the product is published and whether it is locked by a running publish. Body text is left out; get_product returns the full product.

Example response:

```json
{
  "products": [
    {
      "product_id": "6641ab12",
      "title": "Night Owl Club Tee",
      "tags": [
        "owl",
        "ready"
      ],
      "visible": false,
      "is_locked": false
    },
    {
      "product_id": "6641ab13",
      "title": "Coffee First Tee",
      "tags": [
        "coffee"
      ],
      "visible": true,
      "is_locked": false
    }
  ],
  "page": 1,
  "last_page": 3
}
```

### get_product

One product with description, variants, prices in cents, print areas and mockup images. Access: read. REST: `GET /api/v1/printify/shops/{shop_id}/products/{product_id}`. MCP: `printify_read → get_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `product_id` | string | yes | Product ID from list_products. |

Returns one product in full: title, description, tags, every variant with its price in cents and whether it is enabled, the print areas and the mockup images. Use it before editing or publishing.

Example response:

```json
{
  "product_id": "6641ab12",
  "title": "Night Owl Club Tee",
  "description": "Soft unisex tee with the Night Owl Club print.",
  "tags": [
    "owl",
    "ready"
  ],
  "variants": [
    {
      "variant_id": 45740,
      "title": "Black / S",
      "price": 2499,
      "is_enabled": true
    },
    {
      "variant_id": 45742,
      "title": "Black / L",
      "price": 2499,
      "is_enabled": true
    }
  ],
  "images": 6,
  "visible": false
}
```

### list_orders

Orders in a shop with status, total and line items, filtered by status or SKU. Access: read. REST: `GET /api/v1/printify/shops/{shop_id}/orders`. MCP: `printify_read → list_orders`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `status` | string | no | Order status, for example has-issues, on-hold, payment-not-received, in-production or fulfilled. |
| `sku` | string | no | Only orders with at least one product with this SKU. |
| `page` | integer | no | Page number, starting at 1. Default: 1. |

Lists orders of one shop. Filter by status, for example has-issues, on-hold, payment-not-received, in-production or fulfilled, or by SKU. Pages hold 10 orders at most, so page through the results. Totals are in cents.

Example response:

```json
{
  "orders": [
    {
      "order_id": "5a96f649b2439217d070f507",
      "label": "1042",
      "status": "has-issues",
      "total_price": 2499,
      "total_shipping": 450,
      "created_at": "2026-10-16T09:12:00Z"
    }
  ],
  "page": 1,
  "last_page": 1
}
```

### get_order

One order with line item statuses, shipping address, shipments and tracking. Access: read. REST: `GET /api/v1/printify/shops/{shop_id}/orders/{order_id}`. MCP: `printify_read → get_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `order_id` | string | yes | Order ID from list_orders. |

Returns one order in full: the status of each line item, the shipping address, costs in cents and the shipments with carrier and tracking number once they exist. Customer address data is returned, so handle it as personal data.

Example response:

```json
{
  "order_id": "5a96f649b2439217d070f507",
  "label": "1042",
  "status": "has-issues",
  "address_to": {
    "first_name": "Dana",
    "country": "US",
    "city": "Austin"
  },
  "line_items": [
    {
      "product_id": "6641ab12",
      "variant_id": 45740,
      "quantity": 1,
      "status": "has-issues"
    }
  ],
  "total_price": 2499,
  "shipments": []
}
```

### upload_image

Add an image to your Media Library from a URL, to use on products. Access: write. REST: `POST /api/v1/printify/images`. MCP: `printify_write → upload_image`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `file_name` | string | yes | Name shown in the Media Library. |
| `url` | string | yes | Public URL of the image. |

Uploads an image from a public URL to your Printify Media Library and returns its ID, size and type. Reuse the ID on any product. It reaches no customer and you can archive the image later, so it runs without asking first.

Example response:

```json
{
  "image_id": "5d39b159e7c48c000728c89f",
  "file_name": "night-owl.png",
  "width": 4000,
  "height": 4000,
  "mime_type": "image/png"
}
```

### create_product

Create a draft product from a design, blueprint, print provider and variant prices. Access: write. REST: `POST /api/v1/printify/shops/{shop_id}/products`. MCP: `printify_write → create_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `title` | string | yes | Product title. |
| `description` | string | yes | Product description, HTML allowed. |
| `blueprint_id` | integer | yes | Blueprint ID from list_blueprints. |
| `print_provider_id` | integer | yes | Print provider ID from get_blueprint_variants. |
| `variants` | array | yes | Objects with variant id and price in cents. |
| `image_id` | string | yes | Image ID from upload_image, placed on the front print area. |
| `tags` | array | no | Tags as strings. |

Creates a product in one shop from a blueprint and a print provider, with the variants you list and the image placed in the print area. Prices are integers in cents. The product stays a draft: it is not on your sales channel until publish_product runs, so this tool runs without asking first. Blueprint and print provider cannot change afterwards.

Example response:

```json
{
  "product_id": "6641ab12",
  "shop_id": 8123456,
  "title": "Night Owl Club Tee",
  "variants_enabled": 2,
  "visible": false
}
```

### update_product

Change title, description, tags, variant prices or enabled variants of a product. Access: write. REST: `PATCH /api/v1/printify/shops/{shop_id}/products/{product_id}`. MCP: `printify_write → update_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `product_id` | string | yes | Product ID from list_products. |
| `title` | string | no | New title. |
| `description` | string | no | New description, HTML allowed. |
| `tags` | array | no | Replaces the tags. |
| `variants` | array | no | Objects with variant id, price in cents and is_enabled. |

Updates a product in Printify. Prices are integers in cents. The change reaches your sales channel only after publish_product, so a wrong edit is undone with another call and this tool runs without asking first.

Example response:

```json
{
  "product_id": "6641ab12",
  "updated": [
    "variants"
  ],
  "visible": false
}
```

### publish_product

Send a product, or selected details of it, to the connected sales channel store. Access: write, asks the user first. REST: `POST /api/v1/printify/shops/{shop_id}/products/{product_id}/publish`. MCP: `printify_write → publish_product`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `product_id` | string | yes | Product ID from list_products. |
| `title` | boolean | no | Sync the title. Default: true. |
| `description` | boolean | no | Sync the description. Default: true. |
| `images` | boolean | no | Sync the mockup images. Default: true. |
| `variants` | boolean | no | Sync variants and prices. Default: true. |
| `tags` | boolean | no | Sync the tags. Default: true. |

Publishes one product to the shop's sales channel. Choose which details to sync: title, description, images, variants and tags. Printify caps publishing at 200 requests per 30 minutes. The product is locked while it publishes. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "product_id": "6641ab12",
  "status": "publishing",
  "is_locked": true
}
```

### send_order_to_production

Send an order to the print provider, which charges your Printify account. Access: write, asks the user first. REST: `POST /api/v1/printify/shops/{shop_id}/orders/{order_id}/to-production`. MCP: `printify_write → send_order_to_production`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `order_id` | string | yes | Order ID from list_orders. |

Sends one order to production. You need it only when the shop's order approval is manual, because with automatic approval Printify sends orders after 24 hours without a call. Production charges your account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "5a96f649b2439217d070f507",
  "status": "sending-to-production"
}
```

### cancel_order

Cancel an unpaid order. A canceled order allows no further actions. Access: write, asks the user first. REST: `POST /api/v1/printify/shops/{shop_id}/orders/{order_id}/cancel`. MCP: `printify_write → cancel_order`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `shop_id` | integer | yes | Shop ID from list_shops. |
| `order_id` | string | yes | Order ID from list_orders. |

Cancels one order that Printify has not charged yet. It cannot be undone: a canceled order allows no further actions, and your customer may expect it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "order_id": "5a96f649b2439217d070f507",
  "status": "canceled"
}
```

## How do I connect Printify to Claude Code, Codex or Cursor?

Connecting Printify takes three steps: sign up, sign in to Printify once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Printify to your agent.

1. **Create an account** Sign up and add Printify in the console. Your API key is there too.

2. **Sign in to Printify in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Printify there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Printify tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Upload the three PNG files from this folder URL to my Printify media library, then create a draft unisex t-shirt for each one in sizes S to XL, priced at $24.99. Do not publish anything.
```

### Call Printify from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/printify with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PATCH https://cotlet.dev/api/v1/printify/shops/8123456/products/6641ab12 \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"variants":[{"id":45740,"price":2699,"is_enabled":true}]}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "product_id": "6641ab12",
  "updated": [
    "variants"
  ],
  "visible": false
}
```

## Why use Cotlet for Printify?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Printify yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Printify changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Printify to Cotlet?

Yes. You sign in to Printify yourself, in your own Cloud Browser, and we never save your password. Your agents only get Printify once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Printify integration?**

No, Cotlet is independent of Printify. Printify's own API is too limited for this work. Cotlet works through your own Printify account, the way you use Printify in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Printify in your console: your agents lose access at once and you stay signed in. Signing out of Printify in the browser works too, and Reset browser deletes the whole profile.

## Is there a Printify MCP server on GitHub?

Yes. Community Printify MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it a Printify token, and keep it running yourself; when the API changes or your token expires, it stops until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, create a personal access token under My Profile > Connections, add both to each MCP client | Sign up, sign in to Printify once, add one MCP server or API key |
| When Printify changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Printify access | A token with write scopes in a file on your computer, readable by any program you run | Your own Cloud Browser in the EU, session encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you create a new token by hand; tokens last one year | Your Cloud Browser keeps you signed in; if Printify logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Printify changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Printify API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Printify API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Printify account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Printify yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Printify only after you enable it. When Printify signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Printify, sign out of Printify in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Printify's terms:** You use your own Printify account and stay responsible for following Printify's terms. Cotlet is independent and not affiliated with Printify. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Printify in the console and press Request access. Then you create your API key and connect Printify there.

**Do I need to be technical?**

No. You sign in to Printify once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Printify to Cotlet?**

Yes. You sign in to Printify yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Printify once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Printify sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Printify cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Printify's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Printify sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Printify login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Printify offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a Printify token or an OAuth app?**

No. Cotlet works in your own signed-in Printify account. With the public API you would create a personal access token under My Profile > Connections, which lasts one year, or apply for an OAuth app, which Printify reviews for up to 1 week.

**Can the agent cancel or send orders by itself?**

Only if you switch confirmation off for that tool. Sending an order to production charges your account, so both tools ask you first by default. Printify cancels unpaid orders only.

**Can my agent post or send messages in Printify without asking me?**

No. Every call to publish_product, send_order_to_production or cancel_order waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. upload_image, create_product, update_product runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Printify API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/printify from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.