Live

Pixieset API and MCP server

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.

Category: Invoicing & freelance CRM
Endpoints: 13 7 read, 6 write
Updated: 1d ago October 11, 2026

Request access View as Markdown

Your agent

Claude Code, Codex, Cursor or a script
calls a tool
Cotlet

MCP server and REST API · 13 endpoints

cotlet.dev/mcp/v1
acts as you
Pixieset

Signed in as you on pixieset.com

You sign in once. We never store your password.

Official API

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.

What Pixieset's own tools do compared with Cotlet
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 · Pixieset Studio Manager · Pixieset Client Gallery · Zapier: Pixieset has no integration yet · Pixieset Help: How do I upload from Lightroom? · Pixieset Help: Bulk creating collections in Client Gallery

Common use cases

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

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. Your agent calls list_collections, create_collection, upload_photos, get_collection and share_collection.
Export client favorites and notes

Merge all favorite lists in the Lee Family Session gallery into one Lightroom filename list and put the photos with editing notes first. Your agent calls list_collections and list_favorites.
Resend galleries nobody has downloaded 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. Your agent calls list_collections, get_download_activity, list_contacts and share_collection.
List unpaid invoices Runs: Weekly

List my unpaid Pixieset invoices with client, amount and due date. Your agent calls 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. Your agent calls create_contact and create_invoice.
List upcoming booked sessions Runs: Weekly

What sessions do I have booked next week, and with whom? Your agent calls list_sessions.

Endpoints

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.

All endpoints · 13 total

missing one? request an endpoint

POST

list_collections

Client gallery collections with name, event date, photo count and gallery URL.

read

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.

POST /api/v1/pixieset/list_collections

Input

Input: list_collections
Parameter	Type	Description
query	string	Filter by collection name.
limit	integer	1 to 100. Default: 25.
cursor	string	Next page cursor from the previous call.

Example response

{
  "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
}

POST
get_collection

One collection with photo count, privacy settings, cover and gallery URL.
read
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.

POST /api/v1/pixieset/get_collection

Input

Input: get_collection

Parameter Type Description

collection_id required string Collection ID from list_collections.

Example response
```
{
  "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/"
}
```
POST
list_favorites

Photos clients marked as favorites in a collection, with their comments.
read
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.

POST /api/v1/pixieset/list_favorites

Input

Input: list_favorites

Parameter Type Description

collection_id required string Collection ID from list_collections.
with_comments_only boolean Only photos with a client comment.

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

Who downloaded from a collection and when.
read
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.

POST /api/v1/pixieset/get_download_activity

Input

Input: get_download_activity

Parameter Type Description

collection_id required string Collection ID from list_collections.

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

Studio Manager contacts: clients, leads and other connections.
read
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.

POST /api/v1/pixieset/list_contacts

Input

Input: list_contacts

Parameter Type Description

query string Search by name or email.
limit integer 1 to 100. Default: 50.
cursor string Next page cursor from the previous call.

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

Booked sessions in a date range with client, session type and time.
read
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.

POST /api/v1/pixieset/list_sessions

Input

Input: list_sessions

Parameter Type Description

from date Start of the range. Default: today.
to date End of the range. Default: 7 days after from.

Example response
```
{
  "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"
    }
  ]
}
```

Input: list_contacts
Parameter	Type	Description
query	string	Search by name or email.
limit	integer	1 to 100. Default: 50.
cursor	string	Next page cursor from the previous call.

Input: list_sessions
Parameter	Type	Description
from	date	Start of the range. Default: today.
to	date	End of the range. Default: 7 days after from.

POST

list_invoices

Invoices with client, total, amount paid and due date.

read

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.

POST /api/v1/pixieset/list_invoices

Input

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

Example response

{
  "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
}

POST
create_collection

New client gallery collection. Nothing reaches the client until you share it.
write
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.

POST /api/v1/pixieset/create_collection

Input

Input: create_collection

Parameter Type Description

name required string Collection name, e.g. "Smith Wedding".
event_date date Date of the shoot.

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

Add photos to a collection from image URLs.
write
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.

POST /api/v1/pixieset/upload_photos

Input

Input: upload_photos

Parameter Type Description

collection_id required string Collection ID from list_collections.
photo_urls required string[] Image URLs, publicly reachable.

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

Input: create_collection
Parameter	Type	Description
name required	string	Collection name, e.g. "Smith Wedding".
event_date	date	Date of the shoot.

POST

share_collection

Send the branded email invite with the gallery link to one or more clients.

asks first write

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.

POST /api/v1/pixieset/share_collection

Input

Input: share_collection
Parameter	Type	Description
collection_id required	string	Collection ID from list_collections.
emails required	string[]	Recipient emails.
message	string	Personal note in the invite.

Example response

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

POST

create_contact

Add a client or lead to Studio Manager contacts.

write

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.

POST /api/v1/pixieset/create_contact

Input

Input: create_contact
Parameter	Type	Description
name required	string	Full name.
email required	string	Contact email.
phone	string	Phone number.
type	string	Contact type as Studio Manager shows it, e.g. lead or client.

Example response

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

POST

create_invoice

Draft invoice for a contact with line items. Not sent until you send it.

write

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.

POST /api/v1/pixieset/create_invoice

Input

Input: create_invoice
Parameter	Type	Description
contact_id required	string	Contact ID from list_contacts or create_contact.
items required	object	Line items: list of { name, quantity, unit_price }.
due_date	date	Payment due date.

Example response

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

POST
send_invoice

Email a draft invoice to the client with a link to pay online.
asks first write
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.

POST /api/v1/pixieset/send_invoice

Input

Input: send_invoice

Parameter Type Description

invoice_id required string Invoice ID from list_invoices or create_invoice.
message string Note in the email.

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

Input: send_invoice
Parameter	Type	Description
invoice_id required	string	Invoice ID from list_invoices or create_invoice.
message	string	Note in the email.

Setup

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.

MCP REST API

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
Claude Code Cursor Codex
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"
```
Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
4
Ask your agent
Prompt
```
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.
```
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.

1
Export your API key
Shell
```
export COTLET_API_KEY="cotlet_..."
```
Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

Call a tool

curl

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!"}'

Every tool is a POST endpoint at /api/v1/pixieset/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

Read the result

Example response · share_collection

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

You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for Pixieset? Hosted, safe and kept working.

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.

Alternatives

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.

Cotlet compared with a By hand
	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

For AI agents

Cotlet for Pixieset in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

list_collections passing
get_collection passing
list_favorites passing
get_download_activity passing
list_contacts passing

+ 8 more endpoints

13/13 passing latest check self-healing

pixieset.txt

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.

Full page as Markdown

Automations

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 to run Pixieset automations through Cotlet, and how to schedule them
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.

Pricing & limits

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.

See full pricing

Cotlet plan sizes: price, monthly credits and price per credit
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.

About Cotlet

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
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
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
Contact: Questions about the company, security or an app: contact@cotlet.dev

About Cotlet

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.

Give your agent access to Pixieset.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.

Request access

Does Pixieset have an official API?

What can an AI agent do in Pixieset?

Create and share a client gallery

Export client favorites and notes

Resend galleries nobody has downloaded Runs: Weekly

List unpaid invoices Runs: Weekly

Add leads and draft their invoices

List upcoming booked sessions Runs: Weekly

What is the Pixieset API?

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

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

Connect Pixieset over MCP

Create an account

Sign in to Pixieset once

Add Cotlet to your agent

Ask your agent

Call Pixieset over REST

Export your API key

Call a tool

Read the result

Why use Cotlet for Pixieset? Hosted, safe and kept working.

Built for agents

Your login stays yours

You stay in control

Kept working for you

Is there a Pixieset MCP server on GitHub?

Which one fits you

Cotlet for Pixieset in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

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

How much does the Pixieset API cost?

How Cotlet holds your access

Frequently asked questions

How do I get access?

Do I need to be technical?

Is a hosted server safe? My Pixieset session would leave my computer.

Do I need Studio Manager for invoices and sessions?

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

Can I use the Pixieset API in n8n?

Related integrations

Dubsado

PeoplePerHour

SuiteDash

Give your agent access to Pixieset.

Analytics cookies