Pixieset API · unofficial, by Cotlet

Create your own Pixieset API

Pixieset: no public API found (checked 19 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Pixieset account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Pixieset session and returns only what your login can see.

Try it free now

Free 7-day trial, 2,000 credits, no card

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Pixieset. Pixieset is a trademark of its owner. If Pixieset's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/unpaid-invoices" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"due_before": "2026-11-30"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/unpaid-invoices";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ due_before: "2026-11-30" }),
});
const { data } = await res.json();
Python
import os
import requests

key = os.environ["COTLET_API_KEY"]
res = requests.post(
    "https://cotlet.dev/api/v1/custom/unpaid-invoices",
    headers={"Authorization": f"Bearer {key}"},
    json={"due_before": "2026-11-30"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "invoice": "INV-0218",
      "client": "Anna S.",
      "amount": "2400.00",
      "due": "2026-11-24"
    },
    {
      "invoice": "INV-0221",
      "client": "Ben K.",
      "amount": "650.00",
      "due": "2026-11-25"
    }
  ]
}

01 Build

How do you build a Pixieset endpoint with Cotlet?

  1. Sign in to Pixieset in your Cloud Browser.

    You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.

  2. Do the job once with your agent.

    For example: "List the unpaid invoices due this month with the client, amount and due date."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a due date or a client, and the fields it returns.

  4. Call it with your Cotlet API key.

    Each endpoint gets its own address, POST https://cotlet.dev/api/v1/custom/<name>. You send JSON in and get JSON back, from the same signed-in Pixieset session.

02 Endpoints

Example endpoints you could build for Pixieset

Cotlet ships no fixed list of Pixieset endpoints. You decide which endpoints you build and what each one returns.

  • POST /api/v1/custom/unpaid-invoices

    Unpaid invoices

    Invoice, client, amount and due date for each open invoice

  • POST /api/v1/custom/upcoming-sessions

    Upcoming sessions

    Session type, client, date and location for each booking

  • POST /api/v1/custom/gallery-activity

    Gallery activity

    Views, downloads and favorites for a gallery

  • POST /api/v1/custom/client-favorites

    A client's favorites

    File names of the photos a client marked as favorites

  • POST /api/v1/custom/record-payment writes

    Record a payment

    A payment recorded on the invoice you name, with the method

A call to an endpoint you built could look like this:

Request

curl -X POST "https://cotlet.dev/api/v1/custom/unpaid-invoices" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"due_before": "2026-11-30"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "invoice": "INV-0218",
      "client": "Anna S.",
      "amount": "2400.00",
      "due": "2026-11-24"
    },
    {
      "invoice": "INV-0221",
      "client": "Ben K.",
      "amount": "650.00",
      "due": "2026-11-25"
    }
  ]
}

When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.

03 Uses

What can you use your Pixieset endpoints for?

  • Schedule Cotlet endpoint Slack or email

    A Monday list in n8n or Make.

    Unpaid invoices and galleries nobody downloaded, sent to Slack or email.

  • Gallery closes endpoint file list

    Favorites to your editing workflow.

    A client's favorites as a list of file names, ready for a Lightroom collection.

  • Month end endpoint Google Sheets

    A bookkeeping sheet.

    Paid invoices by month, pulled into Google Sheets for your accountant.

  • Chat agent endpoint session and invoice

    Your own AI assistant.

    A chat agent that checks a client's session and invoice before it answers their email.

04 Access

What can an endpoint see and change?

An endpoint works in your own Pixieset session, so it can read and change only what your Pixieset login can. You choose what each endpoint does when you build it.

An endpoint that changes something, such as recording a payment, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.

05 Official API

Does Pixieset have an official API?

Pixieset: no public API and no developer docs found (checked 19 Nov 2026). Zapier says Pixieset "has not yet built an integration on Zapier", and Studio Manager exports contacts to CSV. The full picture with sources: Does Pixieset have an API or MCP server?

Want ChatGPT or Claude to work in Pixieset instead of code? See the Pixieset MCP server.

06 Pricing

What does it cost?

per successful call
10 credits
when a call fails
0
in the smallest pack
≈ 500 calls
free trial, no card
7 days

A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.

Pixieset API with Cotlet: questions

Is this an official Pixieset API?

No. Cotlet is independent and not affiliated with Pixieset. The endpoints you build run in your own signed-in Pixieset account.

Do I need to code?

Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.

What happens when Pixieset changes its screens?

An endpoint works while Pixieset works the way it did when you built it. If Pixieset changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.

How long can a call take?

Up to 90 seconds, and the answer can be up to 1 MB of JSON.

Build your first Pixieset endpoint

Sign in once, do the job with your agent and save it as an endpoint.

Try it free now

No card. Takes about 5 minutes.