Pixifi API · unofficial, by Cotlet

Create your own Pixifi API

Pixifi: no public API found on pixifi.com or academy.pixifi.com (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Pixifi 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 Pixifi 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 Pixifi. Pixifi is a trademark of its owner. If Pixifi's own integrations cover what you need, use them first.

curl
curl -X POST "https://cotlet.dev/api/v1/custom/new-leads" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"since": "2026-11-16"}'
Node.js
const url = "https://cotlet.dev/api/v1/custom/new-leads";
const res = await fetch(url, {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ since: "2026-11-16" }),
});
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/new-leads",
    headers={"Authorization": f"Bearer {key}"},
    json={"since": "2026-11-16"},
)
data = res.json()["data"]
Response 200 OK · JSON
{
  "data": [
    {
      "lead": "Priya and Sam",
      "event": "Barn wedding",
      "event_date": "2027-10-03",
      "status": "new"
    },
    {
      "lead": "Ana and Tom",
      "event": "Garden wedding",
      "event_date": "2027-09-19",
      "status": "new"
    }
  ]
}

01 Build

How do you build a Pixifi endpoint with Cotlet?

  1. Sign in to Pixifi 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 leads since a date with the event type, date and status."

  3. Save it as an endpoint.

    Give it a name, choose its inputs, such as a date or a lead status, 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 Pixifi session.

02 Endpoints

Example endpoints you could build for Pixifi

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

  • POST /api/v1/custom/new-leads

    New leads

    Lead, event type, event date and status since a date

  • POST /api/v1/custom/unsigned-contracts

    Unsigned contracts

    Contract, client and days since sent

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

    Open invoices

    Invoice, client, amount and due date

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

    Upcoming events

    Client, date, venue and package for each event

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

    Record a payment

    A payment recorded on the invoice you name

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

Request

curl -X POST "https://cotlet.dev/api/v1/custom/new-leads" \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"since": "2026-11-16"}'

The answer is JSON, with your fields under data:

Response · 200 OK

{
  "data": [
    {
      "lead": "Priya and Sam",
      "event": "Barn wedding",
      "event_date": "2027-10-03",
      "status": "new"
    },
    {
      "lead": "Ana and Tom",
      "event": "Garden wedding",
      "event_date": "2027-09-19",
      "status": "new"
    }
  ]
}

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 Pixifi endpoints for?

  • Schedule Cotlet endpoint Slack or email

    A Monday list in n8n or Make.

    Unsigned contracts and unpaid invoices, sent to Slack or email.

  • Website form endpoint booked dates

    Leads from your website.

    A new inquiry checked against your booked dates before you reply.

  • Month end endpoint Google Sheets

    A bookkeeping sheet.

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

  • Chat agent endpoint event and invoice

    Your own AI assistant.

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

04 Access

What can an endpoint see and change?

An endpoint works in your own Pixifi session, so it can read and change only what your Pixifi login can. An owner login sees the whole business. A team login sees what its permissions allow. 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 Pixifi have an official API?

Pixifi: no public API or developer docs found (checked 20 Nov 2026). Its Zapier app has 25 triggers, 12 actions and 4 searches. The full picture with sources: Does Pixifi have an API or MCP server?

Want ChatGPT or Claude to work in Pixifi instead of code? See the Pixifi 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.

Pixifi API with Cotlet: questions

Is this an official Pixifi API?

No. Cotlet is independent and not affiliated with Pixifi. The endpoints you build run in your own signed-in Pixifi 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 Pixifi changes its screens?

An endpoint works while Pixifi works the way it did when you built it. If Pixifi 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 Pixifi 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.