# Pixieset API and MCP server

> Pixieset has no public API, no webhooks and no Zapier app (checked 11 Oct 2026). Its Apps & Plugins page lists the Lightroom plugin, the Studio Manager mobile app and Photo Editor, and no developer program.

Platform for photographers: Client Gallery for delivery, proofing and sales, plus Studio Manager for contacts, bookings, invoices, contracts and payments.

## What is the Pixieset API?

Cotlet's Pixieset API exposes 13 endpoints for your own Pixieset account: list collections, get collection, list favorites, get download activity, list contacts, list sessions, list invoices, create collection, upload photos, share collection, create contact, create invoice and send invoice. The list_collections endpoint returns client gallery collections with name, event date, photo count and gallery URL. Each endpoint takes simple JSON inputs like collection_id, limit or cursor and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Invoicing & freelance CRM](https://cotlet.dev/integrations/category/invoicing-freelance-crm)
- **Endpoints:** 13 (7 read, 6 write)
- **Updated:** 2026-10-11

Pixieset has no public API, no webhooks and no Zapier app (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Pixieset with 13 endpoints (7 read, 6 write): your AI agent signs in as you and does the work.

## Does Pixieset have an official API?

Pixieset has no public API, no webhooks and no Zapier app (checked 11 Oct 2026). Its Apps & Plugins page lists the Lightroom plugin, the Studio Manager mobile app and Photo Editor, and no developer program.

| Task | Pixieset official | Cotlet |
|---|---|---|
| List client gallery collections | No | Yes |
| Upload photos into a collection | Partly: The Lightroom plugin uploads and syncs from Lightroom Classic, not from code | Yes |
| Email a gallery invite to a client | No | Yes |
| Read client favorites and comments | No | Yes |
| See who downloaded a gallery | No | Yes |
| Add clients and leads | No: Embedded lead forms on your website add leads, but there is no way to create contacts from code | Yes |
| Create and send invoices | No | Yes |
| List booked sessions | No | Yes |

Sources: [Pixieset Apps & Plugins](https://pixieset.com/apps/), [Pixieset Studio Manager](https://pixieset.com/studio-manager/), [Pixieset Client Gallery](https://pixieset.com/client-gallery/), [Zapier: Pixieset has no integration yet](https://zapier.com/apps/pixieset/integrations), [Pixieset Help: How do I upload from Lightroom?](https://help.pixieset.com/hc/en-us/articles/115003504512-How-do-I-upload-from-Lightroom), [Pixieset Help: Bulk creating collections in Client Gallery](https://help.pixieset.com/hc/en-us/articles/41219071036685-Bulk-creating-collections-in-Client-Gallery)

## For AI agents

```text
Pixieset has no public API, no webhooks and no Zapier app (checked 11 Oct 2026). Its Apps & Plugins page lists the Lightroom plugin, the Studio Manager mobile app and Photo Editor, and no developer program.
Cotlet provides a hosted MCP server and REST API for Pixieset: 13 tools (7 read, 6 write).
Access       Request access at https://cotlet.dev/app/signup?app=pixieset; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/pixieset
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_collections, get_collection, list_favorites, get_download_activity, list_contacts, list_sessions, list_invoices, create_collection, upload_photos, share_collection, create_contact, create_invoice, send_invoice
Confirm      share_collection, send_invoice (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/pixieset-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=pixieset (Pixieset is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Pixieset once in a browser. 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 Pixieset server that someone else maintains, including non-developers.

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.
Session: the user signs in to Pixieset in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Pixieset's terms; Cotlet is not affiliated with Pixieset.
```

## What can an AI agent do in Pixieset?

Cotlet is best for photographers who deliver galleries and invoice clients in Pixieset and want an AI agent to do the repeat steps without running or fixing a server.

- **[Create and share a client gallery](https://cotlet.dev/integrations/pixieset-api-mcp-server/create-and-share-client-gallery)**: "Create a gallery called Smith Wedding dated 4 Oct 2026, upload the photos from the links in links.csv, check that every file made it, then email the invite to anna@example.com." → `list_collections`, `create_collection`, `upload_photos`, `get_collection`, `share_collection`
- **[Export client favorites and notes](https://cotlet.dev/integrations/pixieset-api-mcp-server/export-client-favorites)**: "Merge all favorite lists in the Lee Family Session gallery into one Lightroom filename list and put the photos with editing notes first." → `list_collections`, `list_favorites`
- **[Resend galleries nobody has downloaded](https://cotlet.dev/integrations/pixieset-api-mcp-server/check-gallery-downloads)** (runs: weekly): "Check the galleries I shot in the last 8 weeks, tell me which ones nobody has downloaded, and resend the invite for those." → `list_collections`, `get_download_activity`, `list_contacts`, `share_collection`
- **List unpaid invoices** (runs: weekly): "List my unpaid Pixieset invoices with client, amount and due date." → `list_invoices`
- **Add leads and draft their invoices**: "Add the three leads from inquiries.csv as contacts and draft a $450 retainer invoice for each." → `create_contact`, `create_invoice`
- **List upcoming booked sessions** (runs: weekly): "What sessions do I have booked next week, and with whom?" → `list_sessions`

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

Yes. Cotlet does not replace your automation platform: it gives it a Pixieset 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 resend galleries nobody has downloaded, 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 to https://cotlet.dev/api/v1/pixieset/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/pixieset/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/pixieset/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/pixieset/{tool} 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 403 until the account has an API key with access to Pixieset.

### list_collections

Client gallery collections with name, event date, photo count and gallery URL. Access: read. REST: `POST /api/v1/pixieset/list_collections`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Filter by collection name. |
| `limit` | integer | no | 1 to 100. Default: 25. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the collections in your Client Gallery, newest first. Use query to find one by name, then pass its collection_id to the other tools. Pages hold up to 100 collections; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "collections": [
    {
      "collection_id": "col_5530",
      "name": "Johnson Family Session",
      "event_date": "2026-09-27",
      "photos": 84,
      "url": "https://studioexample.pixieset.com/johnsonfamily/"
    },
    {
      "collection_id": "col_5521",
      "name": "Lee Family Session",
      "event_date": "2026-09-13",
      "photos": 112,
      "url": "https://studioexample.pixieset.com/leefamily/"
    }
  ],
  "next_cursor": null
}
```

### get_collection

One collection with photo count, privacy settings, cover and gallery URL. Access: read. REST: `POST /api/v1/pixieset/get_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |

Returns one collection: name, event date, photo count and gallery URL, plus whether it is password protected and whether downloads need a PIN. It never returns the password or the PIN itself.

Example response:

```json
{
  "collection_id": "col_5530",
  "name": "Johnson Family Session",
  "event_date": "2026-09-27",
  "photos": 84,
  "password_protected": true,
  "download_pin": true,
  "url": "https://studioexample.pixieset.com/johnsonfamily/"
}
```

### list_favorites

Photos clients marked as favorites in a collection, with their comments. Access: read. REST: `POST /api/v1/pixieset/list_favorites`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |
| `with_comments_only` | boolean | no | Only photos with a client comment. |

Returns the photos clients favorited in one collection, with the file name of each and any note or editing request the client added to that image. Set with_comments_only to get only photos that have a comment. Nothing is changed or sent.

Example response:

```json
{
  "collection_id": "col_5521",
  "favorites": [
    {
      "file_name": "IMG_2041.jpg",
      "comment": "Please brighten this one."
    },
    {
      "file_name": "IMG_2077.jpg",
      "comment": null
    }
  ]
}
```

### get_download_activity

Who downloaded from a collection and when. Access: read. REST: `POST /api/v1/pixieset/get_download_activity`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |

Returns the download activity Pixieset shows for one collection: who downloaded and when. An empty list means nobody has downloaded yet. Nothing is changed or sent.

Example response:

```json
{
  "collection_id": "col_5530",
  "downloads": [
    {
      "email": "client@example.com",
      "downloaded_at": "2026-10-03T18:42:00Z"
    }
  ]
}
```

### list_contacts

Studio Manager contacts: clients, leads and other connections. Access: read. REST: `POST /api/v1/pixieset/list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Search by name or email. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists the contacts in Studio Manager with email and phone, newest first. Search by name or email to find the contact_id that create_invoice needs. Pages hold up to 100 contacts; pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": "ct_3071",
      "name": "Maya Brooks",
      "email": "maya@example.com",
      "phone": "+1 555 0100",
      "type": "lead"
    }
  ],
  "next_cursor": null
}
```

### list_sessions

Booked sessions in a date range with client, session type and time. Access: read. REST: `POST /api/v1/pixieset/list_sessions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | Start of the range. Default: today. |
| `to` | date | no | End of the range. Default: 7 days after from. |

Lists sessions from Studio Manager in a date range, earliest first: the ones clients booked on your booking site and the ones you added. Without dates it covers the coming days from today.

Example response:

```json
{
  "sessions": [
    {
      "session_id": "se_8812",
      "client": "Maya Brooks",
      "type": "Family portrait",
      "starts_at": "2026-10-14T10:00:00-07:00"
    },
    {
      "session_id": "se_8820",
      "client": "Tom Reyes",
      "type": "Headshots",
      "starts_at": "2026-10-16T15:30:00-07:00"
    }
  ]
}
```

### list_invoices

Invoices with client, total, amount paid and due date. Access: read. REST: `POST /api/v1/pixieset/list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unpaid_only` | boolean | no | Only invoices that are not fully paid. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists invoices from Studio Manager, newest first, with client, total, amount paid and due date. Set unpaid_only to keep invoices that are not fully paid. Nothing is changed or sent to a client.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_1204",
      "client": "Maya Brooks",
      "total": 450,
      "paid": 0,
      "currency": "USD",
      "due_date": "2026-10-25"
    },
    {
      "invoice_id": "inv_1198",
      "client": "Tom Reyes",
      "total": 300,
      "paid": 100,
      "currency": "USD",
      "due_date": "2026-10-08"
    }
  ],
  "next_cursor": null
}
```

### create_collection

New client gallery collection. Nothing reaches the client until you share it. Access: write. REST: `POST /api/v1/pixieset/create_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Collection name, e.g. "Smith Wedding". |
| `event_date` | date | no | Date of the shoot. |

Creates an empty collection in your Client Gallery and returns its ID and gallery URL. The client is not told anything until share_collection runs. It reaches no one, so it runs without asking.

Example response:

```json
{
  "collection_id": "col_5544",
  "name": "Smith Wedding",
  "event_date": "2026-10-04",
  "photos": 0,
  "url": "https://studioexample.pixieset.com/smithwedding/"
}
```

### upload_photos

Add photos to a collection from image URLs. Access: write. REST: `POST /api/v1/pixieset/upload_photos`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |
| `photo_urls` | string[] | yes | Image URLs, publicly reachable. |

Downloads each image URL and adds it to the collection. Returns how many photos were added and which URLs failed. It reaches no one, so it runs without asking. Storage counts against your Pixieset plan.

Example response:

```json
{
  "collection_id": "col_5544",
  "added": 2,
  "failed": [],
  "photos_total": 2
}
```

### share_collection

Send the branded email invite with the gallery link to one or more clients. Access: write, asks the user first. REST: `POST /api/v1/pixieset/share_collection`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `collection_id` | string | yes | Collection ID from list_collections. |
| `emails` | string[] | yes | Recipient emails. |
| `message` | string | no | Personal note in the invite. |

Sends Pixieset's branded email invite with the gallery link to the addresses you give, with an optional personal note. The email goes out from your studio. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "collection_id": "col_5544",
  "status": "shared",
  "recipients": 1,
  "gallery_url": "https://studioexample.pixieset.com/smithwedding/",
  "sent_at": "2026-10-12T10:15:00-07:00"
}
```

### create_contact

Add a client or lead to Studio Manager contacts. Access: write. REST: `POST /api/v1/pixieset/create_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Full name. |
| `email` | string | yes | Contact email. |
| `phone` | string | no | Phone number. |
| `type` | string | no | Contact type as Studio Manager shows it, e.g. lead or client. |

Adds one contact to Studio Manager and returns its contact_id. Nothing is sent to the person. It reaches no one, so it runs without asking.

Example response:

```json
{
  "contact_id": "ct_3071",
  "name": "Maya Brooks",
  "email": "maya@example.com",
  "type": "lead"
}
```

### create_invoice

Draft invoice for a contact with line items. Not sent until you send it. Access: write. REST: `POST /api/v1/pixieset/create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_id` | string | yes | Contact ID from list_contacts or create_contact. |
| `items` | object | yes | Line items: list of { name, quantity, unit_price }. |
| `due_date` | date | no | Payment due date. |

Creates a draft invoice for one contact from line items and returns its invoice_id and total. The client gets nothing until send_invoice runs. It reaches no one, so it runs without asking.

Example response:

```json
{
  "invoice_id": "inv_1204",
  "contact_id": "ct_3071",
  "status": "draft",
  "total": 450,
  "currency": "USD",
  "due_date": "2026-10-25"
}
```

### send_invoice

Email a draft invoice to the client with a link to pay online. Access: write, asks the user first. REST: `POST /api/v1/pixieset/send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice ID from list_invoices or create_invoice. |
| `message` | string | no | Note in the email. |

Emails the invoice to the client so they can pay online. This asks the client for money. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_1204",
  "status": "sent",
  "sent_to": "maya@example.com",
  "sent_at": "2026-10-12T10:20:00-07:00"
}
```

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

Connecting Pixieset takes three steps: request access, sign in to Pixieset once, then add one MCP server or call the REST API with the same key.

### Connect Pixieset to your agent.

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

2. **Sign in to Pixieset once** Open the connect page from the console and sign in to Pixieset the way you always do. We keep the session, never your password, and you can revoke it anytime.

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 Pixieset 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.

```
Create a gallery called Smith Wedding dated 4 Oct 2026, upload the photos from the links in links.csv, check that every file made it, then email the invite to anna@example.com.
```

### Call Pixieset 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 a POST endpoint at /api/v1/pixieset/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/pixieset/share_collection \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"collection_id":"col_5544","emails":["client@example.com"],"message":"Your wedding photos are ready!"}'
```

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

```
{
  "collection_id": "col_5544",
  "status": "shared",
  "recipients": 1,
  "gallery_url": "https://studioexample.pixieset.com/smithwedding/",
  "sent_at": "2026-10-12T10:15:00-07:00"
}
```

## Why use Cotlet for Pixieset?

**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 Pixieset yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

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

## Is there a Pixieset MCP server on GitHub?

No MCP server and no Zapier app exist for Pixieset. The realistic options are doing the work by hand in the web app, or writing your own script against internal endpoints that Pixieset does not document.

|  | By hand | Cotlet |
|---|---|---|
| Setup | None: open Pixieset and click | Request access, sign in to Pixieset once, add one MCP server or API key |
| Repeat work | Every gallery, invite and invoice is typed and clicked again | Your agent or script runs the same steps from one prompt |
| When Pixieset changes | You relearn the screens | Our team tests it daily and fixes it for you; failed calls are free |
| Your Pixieset session | In your browser | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | You sign in again | Your agent gets a link to sign in again |
| Where it runs | Your browser, while you sit there | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### 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 Pixieset 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 the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Pixieset API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Pixieset API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

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

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Pixieset yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Pixieset tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Pixieset in your dashboard: the session is deleted and access ends at once. 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.
- **Pixieset's terms:** You use your own Pixieset account and stay responsible for following Pixieset's terms. Cotlet is independent and not affiliated with Pixieset. [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?**

Request access and pick Pixieset. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Pixieset once in your browser 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 a hosted server safe? My Pixieset session would leave my computer.**

Cotlet keeps your Pixieset session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need Studio Manager for invoices and sessions?**

Invoices, contacts and bookings are Studio Manager features, so those tools need Studio Manager on your account (checked 11 Oct 2026). Collections, favorites and downloads are Client Gallery features.

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

No. Every call to share_collection or send_invoice waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_collection, upload_photos, create_contact, create_invoice runs without asking, because it sends nothing to anyone and one call undoes it.

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

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/pixieset/{tool} from the HTTP Request node.