Creators & communities
ShootProof
Client galleries, orders, contracts and invoices in ShootProof.
10 endpoints
Pixifi publishes no public API documentation and no MCP server (checked 16 Nov 2026). Cotlet runs a hosted Pixifi MCP server with 38 tools that ChatGPT and Claude use in your own studio account. Proposals, contracts, invoices and anything else that reaches a client wait for your OK.
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.
38 tools Read and write
Pixifi publishes no public API documentation, and pixifi.com/api answers 404. In its 1 November 2023 webinar Pixifi described its API as bespoke, with keys issued to partner vendors. No Pixifi MCP server and no official ChatGPT or Claude connector was found.
| What you need | Pixifi API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server found | Copy and paste | Hosted MCP server |
| Start today with your own login | Keys for partner vendors | Your login | Your login, once |
| Proposals, contracts, invoices and payments | No public endpoints | One screen at a time | 38 tools, writes after your OK |
| Run from n8n or a script | No public docs | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Pixifi pricing and FAQ · Pixifi webinar transcript, 1 Nov 2023 · Pixifi Academy · Academy: Add and edit a client · Academy: Manage your lead pipeline · Academy: Create and send a proposal · Academy: Contract for an event · Academy: Invoice for an event · Academy: Accounts Receivable · Academy: Refund a client · Academy: Assign staff to an event · Academy: Create a workshop
Once, in a browser we host for you.
One address in its settings.
Draft the proposal, then approve it.
Your agent works in your own signed-in Cloud Browser. Writes, and anything that reaches a client, wait for your OK. Who can see your session
Sign in to Pixifi in a Cloud Browser. Open www.pixifi.com/admin in your Cotlet Cloud Browser and log in with your own Pixifi username.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Pixifi shares the address https://cotlet.dev/mcp/v1 with every other app you turn on, so one connector reaches all of them. Turned Pixifi on later? Refresh the connector and the 38 Pixifi tools show up.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: view_accounts_receivable One tool per owner workflow in Pixifi Academy. Many take an `action`: `list` and `get` only read, the other actions write and ask first.
Contacts > Clients and Leads. Moving a lead to a new status starts the automations you attached to that status.
Reads Contacts > Clients with Filter Options applied. Pixifi saves the filter you last used and shows it again next time you open the list, in the app too. It changes no client, so it runs without asking.
MCP callpixifi_read → filter_clients
REST endpointGET https://cotlet.dev/api/v1/pixifi/clients/filter
| Name | Type | Description |
|---|---|---|
| filters object | object | Filter Options fields as Pixifi labels them, for example brand, category or created date. Leave empty to list all. |
{
"filters": {
"category": "Wedding 2027"
},
"clients": [
{
"name": "Example Couple",
"email": "couple@example.com",
"category": "Wedding 2027"
},
{
"name": "Sample Family",
"email": "family@example.com",
"category": "Wedding 2027"
}
]
} Follows Contacts > Clients > Actions. A record opens in View mode, where the common fields are editable; the Edit toggle shows the rest, events included. Fields you leave out stay as they are. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_clients
REST endpointPOST https://cotlet.dev/api/v1/pixifi/clients/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `create`, `update`. `list` and `get` only read. |
| client string | string | Client name or ID, for `get` and `update`. |
| quick boolean | boolean | For `create`: true for Add a Quick Client with the basic fields, false for the full Add a New Client form. |
| fields object | object | For `create` and `update`: the client form fields in Pixifi's labels, such as name, email and phone. |
{
"action": "action"
} {
"client": "Example Couple",
"email": "couple@example.com",
"phone": "+1 555 0142",
"saved": true
} Runs Contacts > Clients > Actions > Import Clients, sets the brand, category and column mapping, then Import Data. The agent shows you the mapping first, because an import adds every row at once. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → import_clients
REST endpointPOST https://cotlet.dev/api/v1/pixifi/clients
| Name | Type | Description |
|---|---|---|
| file_url string required | string | Link the Cloud Browser can download the .csv from. Pixifi takes only .csv. |
| brand string required | string | Brand the new clients are assigned to. |
| category string | string | Category applied to every imported client, if any. |
| columns object | object | Which .csv column fills which Pixifi client field. |
{
"file_url": "https://example.com",
"brand": "brand"
} {
"file": "clients-2026.csv",
"brand": "Example Studio",
"category": "Imported",
"imported": 48
} Follows Contacts > Leads > Actions. Add New Lead takes more event and contact information than the Quick Lead form. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_leads
REST endpointPOST https://cotlet.dev/api/v1/pixifi/leads/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `create`, `update`. `list` and `get` only read. |
| lead string | string | Lead name or ID, for `get` and `update`. |
| quick boolean | boolean | For `create`: true for Add Quick Lead, false for Add New Lead with event and contact details. |
| fields object | object | Lead fields in Pixifi's labels, such as name, email, event type and date. |
{
"action": "action"
} {
"lead": "Sample Engagement",
"email": "lead@example.com",
"event_type": "Engagement",
"event_date": "2027-05-15",
"saved": true
} Statuses, their names, colours and order are your own. Moving a lead starts any automation you attached to the new status at once, so the agent names that status before it moves the lead. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_lead_pipeline
REST endpointPOST https://cotlet.dev/api/v1/pixifi/lead-pipeline/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `move`. `list` and `get` only read. |
| lead string | string | Lead to move, for `move`. |
| status string | string | Target status column, in your own status names. |
{
"action": "action"
} {
"pipeline": [
{
"status": "New inquiry",
"leads": 4
},
{
"status": "Proposal sent",
"leads": 2
},
{
"status": "Booked",
"leads": 1
}
]
} Follows Settings > Brands > your brand > Inquiry > Create New Form. Returns the View link to share and the Embed snippet for your website. Leads that fill it in land in Pixifi. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → create_inquiry_form
REST endpointPOST https://cotlet.dev/api/v1/pixifi/inquiry-forms
| Name | Type | Description |
|---|---|---|
| brand string required | string | Brand the form belongs to. |
| name string required | string | Form name. |
| fields array required | array | Form fields in order, from the field list Pixifi offers. |
{
"brand": "brand",
"name": "Jane Doe",
"fields": "fields"
} {
"brand": "Example Studio",
"form": "Wedding inquiry",
"view_url": "https://www.pixifi.com/forms/example",
"embed": "<script src=\"...\">",
"saved": true
} What clients see and book on their own: services with time slots and prices, pricing pages with packages, and product templates.
A booking page lets clients and leads pick a date and time for a service. The service settings decide who is scheduled, the price and tax, and which contract, event and invoice each booking creates. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_booking_pages
REST endpointPOST https://cotlet.dev/api/v1/pixifi/booking-pages/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create_service`. `list` and `get` only read. |
| booking_page string | string | Booking page name. |
| service object | object | For `create_service`: name, fixed time slots and duration, assigned staff, price and taxable, show as sold out when full, and the contract, event and invoice titles. |
{
"action": "action"
} {
"booking_page": "Mini sessions",
"service": "Fall mini session",
"duration_minutes": 20,
"price": 175,
"staff": [
"Owner"
],
"saved": true
} Uses Show Advanced Options on the service in Settings > Booking Pages. Clients see the change on the booking page at once. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → set_service_availability
REST endpointPUT https://cotlet.dev/api/v1/pixifi/service-availability
| Name | Type | Description |
|---|---|---|
| booking_page string required | string | Booking page. |
| service string required | string | Service on that page. |
| days array required | array | Days with `available` true or false, and optional time and price difference. A negative price difference makes that day cheaper. |
{
"booking_page": "booking page",
"service": "service",
"days": "days"
} {
"booking_page": "Mini sessions",
"service": "Fall mini session",
"days": [
{
"day": "Saturday",
"available": true,
"price_difference": 0
},
{
"day": "Sunday",
"available": true,
"price_difference": -25
}
],
"saved": true
} Settings > Pricing Pages. Clients see the page at its URL as soon as it is saved. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_pricing_pages
REST endpointPOST https://cotlet.dev/api/v1/pixifi/pricing-pages/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `add_package`. `list` and `get` only read. |
| page object | object | For `create`: page name, page URL, description and tax. |
| pricing_page string | string | For `add_package`: the page. |
| package object | object | For `add_package`: a package template, or a name and price. |
{
"action": "action"
} {
"pricing_page": "Wedding collections",
"url": "weddings",
"packages": [
{
"name": "Half day",
"price": 1900
},
{
"name": "Full day",
"price": 3200
}
],
"saved": true
} Templates > Product & Service Templates > Product Templates. Images on a template show on your pricing, proposal and booking pages. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_product_templates
REST endpointPOST https://cotlet.dev/api/v1/pixifi/product-templates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| type string | string | Product type, for `create`. |
| name string | string | Product name. |
| price number | number | Price. |
{
"action": "action"
} {
"template": "10x10 lay-flat album",
"type": "Album",
"price": 650,
"saved": true
} The calendar, staff and roles, wedding day timelines, reminders, workflows, locations and the miles you drive.
Reads Things to Do > Events. Returns each event with date, type and client. It changes nothing and runs without asking.
MCP callpixifi_read → view_events
REST endpointGET https://cotlet.dev/api/v1/pixifi/events/view
| Name | Type | Description |
|---|---|---|
| view string | string | `day`, `week` or `listing`. Default `listing`. |
| filters object | object | Filter Options fields, such as date range, event type or status. |
| stats boolean | boolean | True to add the Stats totals of the events found. |
{
"view": "listing",
"events": [
{
"event": "Example Couple wedding",
"type": "Wedding",
"date": "2027-06-12"
},
{
"event": "Sample Family portraits",
"type": "Portrait",
"date": "2026-11-22"
}
]
} Pixifi adds events from Quick Actions, the Events calendar, listing or pipeline, a date on the calendar or the client record; the tool uses the same form. Settings you leave out can be edited later. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_events
REST endpointPOST https://cotlet.dev/api/v1/pixifi/events/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `create`, `update`. `list` and `get` only read. |
| event string | string | Event name or ID, for `get` and `update`. |
| fields object | object | Event Name and Event Type are required for `create`; client, date, brand and the rest are optional. |
{
"action": "action"
} {
"event": "Example Couple wedding",
"event_type": "Wedding",
"date": "2027-06-12",
"client": "Example Couple",
"saved": true
} Runs Assign Staff on the event. On the Essential plan you can only assign yourself, so the call fails there for anyone else. After the assignment you can add contracts and questionnaires for that person in Pixifi. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → assign_event_staff
REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-staff/assign
| Name | Type | Description |
|---|---|---|
| event string required | string | Event name or ID, as view_events returns it. |
| staff string required | string | Staff member. Pixifi shows whether they are free for the event. |
| role string required | string | Staff role, for example Second shooter. |
| auto_confirm boolean | boolean | False makes the staff member confirm their participation themselves. |
{
"event": "event",
"staff": "staff",
"role": "role"
} {
"event": "Example Couple wedding",
"staff": "Second Shooter A",
"role": "Second shooter",
"auto_confirm": false,
"saved": true
} Templates live in Things to Do > Timelines > Templates. `apply` adds the template, or the items you give, to the event's Timelines tab, where you can share it with your clients. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_timelines
REST endpointPOST https://cotlet.dev/api/v1/pixifi/timelines/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list_templates`, `create_template`, `apply`. `list` and `get` only read. |
| template string | string | Timeline template name. |
| items array | array | For `create_template`: timeline items with time and title. |
| event string | string | For `apply`: the event that gets the timeline. |
{
"action": "action"
} {
"event": "Example Couple wedding",
"template": "Wedding day, 8 hours",
"items": [
{
"time": "14:00",
"title": "Getting ready"
},
{
"time": "16:30",
"title": "Ceremony"
},
{
"time": "18:00",
"title": "Family portraits"
}
],
"saved": true
} Adds a template under Events > Reminders. You then choose it when you create or edit an event, and from then on Pixifi emails your client on its own. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → create_event_reminders
REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-reminders
| Name | Type | Description |
|---|---|---|
| name string required | string | Reminder template name. |
| reminders array required | array | Each reminder with the email template it sends and when. |
{
"name": "Jane Doe",
"reminders": "reminders"
} {
"reminder": "Session reminders",
"reminders": [
{
"email_template": "Your session is next week",
"when": "7 days before"
},
{
"email_template": "See you tomorrow",
"when": "1 day before"
}
],
"saved": true
} Runs Workflow > Apply Workflow on the event and saves it. The workflow's steps then run on that event as you set them up in Pixifi. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → apply_event_workflow
REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-workflow/apply
| Name | Type | Description |
|---|---|---|
| event string required | string | Event name or ID, as view_events returns it. |
| workflow string required | string | Workflow template to apply. |
{
"event": "event",
"workflow": "workflow"
} {
"event": "Example Couple wedding",
"workflow": "Wedding client journey",
"applied": true
} Uses Add Mileage on the event's Locations. A mileage expense shows under the event's Money. `list` reads Finances > Mileage, the report of all mileage you can export for your accounting. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → add_event_mileage
REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-mileages
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`. `list` and `get` only read. |
| event string | string | Event, for `add`. |
| miles number | number | Distance driven. |
| as_expense boolean | boolean | True to log it as an expense on the event as well. |
{
"action": "action"
} {
"event": "Example Couple wedding",
"miles": 46,
"as_expense": true,
"saved": true
} Things to Do > Events > Locations. An import assigns a brand and maps the .csv columns to location fields, like the client import. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_locations
REST endpointPOST https://cotlet.dev/api/v1/pixifi/locations/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `import`. `list` and `get` only read. |
| name string | string | Location Name, the one required field for `add`. |
| fields object | object | Optional address and notes. |
| file_url string | string | For `import`: the .csv to import. |
{
"action": "action"
} {
"location": "Riverside Park gazebo",
"saved": true
} Everything a client signs or fills in, and the templates behind it. Sending waits for your OK.
A Pixifi proposal bundles a contract, booking page, package choices, add-ons and an invoice built from the payment terms. The agent applies the template, shows you what the client will see, then sends it. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → send_proposals
REST endpointPOST https://cotlet.dev/api/v1/pixifi/proposals
| Name | Type | Description |
|---|---|---|
| recipient string required | string | Lead or client. |
| template string required | string | Proposal template from Templates > Proposals. |
| send_by string | string | `email`, `sms` or `none` to prepare it only. |
{
"recipient": "recipient",
"template": "template"
} {
"recipient": "Sample Engagement",
"template": "Wedding collections",
"send_by": "email",
"sent": false
} Runs Contracts > Create New Contract on the event. The event's brand fills in on its own. A sent contract reaches your client for signing. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → send_event_contracts
REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-contracts
| Name | Type | Description |
|---|---|---|
| event string required | string | Event name or ID, as view_events returns it. |
| template string required | string | Contract template. |
| invoice string | string | Invoice the contract refers to. Pixifi preselects the event's latest one. |
| send boolean | boolean | True to send it to the client after saving. |
{
"event": "event",
"template": "template"
} {
"event": "Example Couple wedding",
"contract": "Wedding contract 2027",
"invoice": "INV-1042",
"sent": false
} Templates > Contract Templates. The agent pastes the wording you give; it does not write legal terms for you. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → create_contract_templates
REST endpointPOST https://cotlet.dev/api/v1/pixifi/contract-templates
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`. `list` and `get` only read. |
| name string | string | Template name. |
| type string | string | `Event` or `Project`. The type sets which variables the contract can use. |
| body string | string | Your contract text, pasted in as you wrote it. |
{
"action": "action"
} {
"template": "Wedding contract 2027",
"type": "Event",
"saved": true
} Templates live under Questionnaires in your template listing. Sending one reaches your client. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → send_questionnaires
REST endpointPOST https://cotlet.dev/api/v1/pixifi/questionnaires
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `send`. `list` and `get` only read. |
| title string | string | Questionnaire title. |
| questions array | array | For `create`: labels, text inputs, text areas and multiple choice questions, each optionally required. |
| recipient string | string | For `send`: the lead or client. |
{
"action": "action"
} {
"title": "Headshot portrait",
"questions": 4,
"recipient": "Sample Client",
"sent": false
} Templates > Emails & SMS > Add Email Template. Reminders, portal invitations and proposals use these templates. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_email_templates
REST endpointPOST https://cotlet.dev/api/v1/pixifi/email-templates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| name string | string | Template name. |
| type string | string | Template Type. It decides which variables the template can use. |
| subject string | string | Subject, variables allowed. |
| body string | string | Message, variables allowed. |
{
"action": "action"
} {
"template": "Your session is next week",
"type": "Event",
"subject": "See you soon, {client first name}",
"saved": true
} Finances > Money. A refund is recorded in Pixifi; you send the money back in Stripe or Square yourself.
Runs Invoices > Create New Invoice on the event, then fills the invoice editor. Creating does not send anything; send_invoices does. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_event_invoices
REST endpointPOST https://cotlet.dev/api/v1/pixifi/event-invoices/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`. `list` and `get` only read. |
| event string | string | Event the invoice belongs to. |
| issue_date string | string | ISO date. |
| due_date string | string | ISO date. |
| lines array | array | For `create`: products from your product list, or manual lines with description and amount. |
{
"action": "create",
"event": "Example Couple wedding",
"issue_date": "2026-11-16",
"due_date": "2027-05-12",
"lines": [
{
"description": "Full day coverage",
"amount": 3200
},
{
"description": "Engagement session",
"amount": 450
}
]
} {
"event": "Example Couple wedding",
"invoice": "INV-1042",
"lines": [
{
"description": "Full day coverage",
"amount": 3200
},
{
"description": "Engagement session",
"amount": 450
}
],
"total": 3650,
"saved": true
} Opens the invoice with VIEW and sends it the way you choose. A sent invoice reaches your client and asks them to pay. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → send_invoices
REST endpointPOST https://cotlet.dev/api/v1/pixifi/invoices
| Name | Type | Description |
|---|---|---|
| invoice string required | string | Invoice number. |
| send_by string | string | A sending option Pixifi offers on the invoice view, or `link` to only return the link. |
{
"invoice": "invoice"
} {
"invoice": "INV-1042",
"client": "Example Couple",
"total": 3650,
"link": "https://www.pixifi.com/invoice/example",
"sent": false
} Finances > Money > Accounts Receivable. Unpaid payments are the Required Payments on invoices that are still open; invoice balances are invoices with money left to pay. It changes nothing and runs without asking.
MCP callpixifi_read → view_accounts_receivable
REST endpointGET https://cotlet.dev/api/v1/pixifi/accounts-receivables/view
| Name | Type | Description |
|---|---|---|
| year number | number | Year. Default this year. |
| tab string | string | `unpaid_payments` or `invoice_balances`. Default `invoice_balances`. |
{
"year": 2026,
"tab": "invoice_balances",
"invoices": [
{
"invoice": "INV-1042",
"client": "Example Couple",
"balance": 2650
},
{
"invoice": "INV-1039",
"client": "Sample Family",
"balance": 450
},
{
"invoice": "INV-1031",
"client": "Example Brand",
"balance": 1200
}
]
} Finances > Money > Payments Received. Batch Update can delete payments, so the agent lists the selected ones before it runs. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_payments_received
REST endpointPOST https://cotlet.dev/api/v1/pixifi/payments-received/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `batch_update`. `list` and `get` only read. |
| year number | number | Year to read. Default this year. |
| filters object | object | Category, brand, type, account or date range. |
| payment object | object | For `add`: amount, date, type and invoice. |
| change string | string | For `batch_update`: brand, payment type, payment category, add a fee expense, or delete. |
{
"action": "action"
} {
"year": 2026,
"payments": [
{
"client": "Example Couple",
"amount": 1000,
"type": "Retainer",
"date": "2026-10-02"
},
{
"client": "Sample Family",
"amount": 350,
"type": "Card",
"date": "2026-11-08"
}
]
} Follows Pixifi's refund steps: Add Paid Payment with a negative amount and Payment Type Refund. Pixifi does not move the money: you issue the refund yourself in Stripe or Square. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → record_refund
REST endpointPOST https://cotlet.dev/api/v1/pixifi/refunds
| Name | Type | Description |
|---|---|---|
| invoice string required | string | Invoice the refund belongs to. |
| amount number required | number | Refund amount. The tool enters it as a negative number. |
{
"invoice": "invoice",
"amount": 1
} {
"invoice": "INV-1042",
"amount": -200,
"payment_type": "Refund",
"saved": true
} Finances > Money > Expenses, where Pixifi charts the year by expense category and against payments. Batch Update can delete, so the agent lists the selected expenses first. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_expenses
REST endpointPOST https://cotlet.dev/api/v1/pixifi/expenses/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `add`, `duplicate`, `batch_update`. `list` and `get` only read. |
| year number | number | Year to read. |
| expense object | object | For `add`: amount, date, vendor, category and account. |
| change string | string | For `batch_update`: brand, vendor, expense category, account, or delete. |
{
"action": "action"
} {
"year": 2026,
"by_category": [
{
"category": "Gear",
"total": 2180
},
{
"category": "Travel",
"total": 640
},
{
"category": "Software",
"total": 410
}
]
} Finances > Money > Profit & Loss: total revenue, sales tax collected, expenses paid and gross margin for the year. It changes nothing and runs without asking.
MCP callpixifi_read → view_profit_and_loss
REST endpointGET https://cotlet.dev/api/v1/pixifi/profit-and-loss/view
| Name | Type | Description |
|---|---|---|
| year number | number | Calendar year. Default this year. |
| filters object | object | Filter Options, such as brand. |
| export string | string | `csv` or `pdf` to return the exported report. |
{
"year": 2026,
"revenue": 48200,
"sales_tax_collected": 1960,
"expenses": 9850,
"gross_margin": 38350
} Longer jobs with tracked time, the task list, your vendor list, and workshops with tickets (Studio Pro plan or higher).
Projects hold work that is not a single event, with tasks and time. The tool uses the same Add Project form as the Projects module. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_projects
REST endpointPOST https://cotlet.dev/api/v1/pixifi/projects/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`. `list` and `get` only read. |
| client string | string | Client the project is for. |
| fields object | object | Project name and the other project fields. |
{
"action": "action"
} {
"project": "Example Brand product catalog",
"client": "Example Brand",
"saved": true
} `summary` reads Time Tracking: time by task, invoiced against not invoiced, billable against non-billable. `invoice` runs Invoice Time, which puts the billable entries on an invoice. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → track_project_time
REST endpointPOST https://cotlet.dev/api/v1/pixifi/project-time/track
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `summary`, `add`, `invoice`. `list` and `get` only read. |
| project string required | string | The project. |
| task string | string | For `add`: the task the time is for. |
| hours number | number | For `add`: hours worked. |
| billable boolean | boolean | For `add`: billable or not. |
{
"action": "action",
"project": "project"
} {
"project": "Example Brand product catalog",
"hours": {
"total": 14.5,
"billable": 12,
"invoiced": 6
}
} Things to Do > Tasks. Batch Update changes every selected task in one step, so the agent lists them for you first. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_tasks
REST endpointPOST https://cotlet.dev/api/v1/pixifi/tasks/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `batch_update`. `list` and `get` only read. |
| title string | string | Task title, for `create`. |
| fields object | object | For `create`: assignee, due date and the other task fields. |
| tasks array | array | For `batch_update`: the tasks to change. |
| change object | object | For `batch_update`: the change Batch Update Tasks applies to all of them. |
{
"action": "action"
} {
"tasks": [
{
"title": "Cull Example Couple engagement",
"due": "2026-11-20",
"done": false
},
{
"title": "Order album proofs",
"due": "2026-11-24",
"done": false
}
]
} Contacts > Vendors. `get` also shows which events the vendor has been linked to over the years. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_vendors
REST endpointPOST https://cotlet.dev/api/v1/pixifi/vendors/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`. `list` and `get` only read. |
| name string | string | Vendor name. |
| type string | string | Vendor type, for example Florist or Venue. |
| category string | string | Vendor category. |
{
"action": "action"
} {
"vendor": "Example Florals",
"type": "Florist",
"category": "Preferred",
"events_linked": 6
} Things to Do > Workshops. Pixifi marks Workshops as Pro: it needs the Studio Pro plan or higher. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_workshops
REST endpointPOST https://cotlet.dev/api/v1/pixifi/workshops/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`. `list` and `get` only read. |
| brand string | string | Brand of the workshop. |
| name string | string | Workshop name. |
| start_date string | string | ISO date. |
| end_date string | string | ISO date. |
| capacity number | number | Maximum capacity. |
| description string | string | Description shown on the workshop page. |
{
"action": "action"
} {
"workshop": "Off-camera flash basics",
"start_date": "2027-03-06",
"end_date": "2027-03-06",
"capacity": 12,
"saved": true
} Ticket quantities may add up to more than the workshop's capacity, but buyers can never take more places than the capacity. Tickets go on sale on the workshop page. By default you confirm each call; you can switch that off for this tool.
MCP callpixifi_write → manage_workshop_tickets
REST endpointPOST https://cotlet.dev/api/v1/pixifi/workshop-tickets/manage
| Name | Type | Description |
|---|---|---|
| workshop string required | string | The workshop. |
| name string required | string | Ticket name. |
| price number | number | Price per ticket. Leave out for a free workshop. |
| quantity number required | number | Tickets available. |
| payment_terms string | string | Payment Terms Template. Without one the buyer pays the full price. |
{
"workshop": "workshop",
"name": "Jane Doe",
"quantity": 1
} {
"workshop": "Off-camera flash basics",
"ticket": "General admission",
"price": 149,
"quantity": 12,
"saved": true
} Your signed-in Pixifi browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 38 Pixifi tools. The session cookie stays in the Cloud Browser.
The clients, events and money records your Pixifi user and plan can open, and nothing more.
Your Pixifi settings and staff permissions, the Twilio SMS setup, payment processor accounts and the dashboard layout.
You log in again yourself, in the same Cloud Browser. Two-factor sign-in stays with you.
Disable Pixifi for agents, reset the browser, or change your Pixifi password.
Cotlet never sees or stores your password: you type it yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Client, lead, event or task fields | Call the same tool again with the earlier values |
| Lead moved to the wrong status | Move it back; automations of the wrong status may already have run |
| Proposal, contract or invoice sent | Already with your client: talk to them before you change it |
| Payments or expenses batch deleted | Add them again from your records; Pixifi has no undo for a batch delete |
All 34 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 4 read tools (clients, the calendar, accounts receivable and the P&L) run at once.
{
"name": "manage_event_invoices",
"arguments": {
"action": "create",
"event": "Example Couple wedding",
"issue_date": "2026-11-16",
"due_date": "2027-05-12",
"lines": [
{
"description": "Full day coverage",
"amount": 3200
},
{
"description": "Engagement session",
"amount": 450
}
]
}
} curl -X POST https://cotlet.dev/api/v1/pixifi/event-invoices/manage \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"action":"create","event":"Example Couple wedding","issue_date":"2026-11-16","due_date":"2027-05-12","lines":[{"description":"Full day coverage","amount":3200},{"description":"Engagement session","amount":450}]}' {
"event": "Example Couple wedding",
"invoice": "INV-1042",
"lines": [
{
"description": "Full day coverage",
"amount": 3200
},
{
"description": "Engagement session",
"amount": 450
}
],
"total": 3650,
"saved": true
} The example bills $3,200 for full day coverage and $450 for the engagement session: $3,650. Nothing is sent to the couple until send_invoices runs. A cron job or n8n flow makes the same call over REST at /api/v1/pixifi with the same key and price. Failed calls are free.
About $27 a monthfor a studio shooting about eight sessions a month, 4,700 credits. Your Pixifi plan stays as it is.
| Job | Calls | Credits |
|---|---|---|
| New inquiries into leads and proposals | 2 × 25 | 500 |
| Contracts, timelines and staff for booked shoots | 3 × 8 | 240 |
| Event invoices created and sent | 2 × 16 | 320 |
| Monday receivables check and reminders | 4 × 4 | 160 |
| Payments received and expenses entered | 1 × 80 | 800 |
| Weekly calendar and task review | 2 × 4 | 80 |
| Questionnaires sent before sessions | 1 × 20 | 200 |
| Client and lead lookups | 1 × 90 | 900 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 320 calls | 4,700 |
The smallest pack, 5,000 credits for $29, covers this month. A busy wedding season uses more calls.
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $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.
| Option | What it does | Where it stops |
|---|---|---|
| Pixifi API | Described by Pixifi in 2023 as keys issued to partner vendors. | No public documentation or self-serve key for a studio. |
| Zapier integration | Listed by Pixifi among its integrations. | Trigger and action recipes you set up in Zapier, not an agent working in Pixifi. |
| Pixifi mobile apps | Schedule, client information and invoices on iOS and Android. | Your hands on the phone; no AI agent route. |
| By hand | Open each client, event and invoice in Pixifi. | One screen at a time, only while you are at the desk. |
If one of Pixifi's own integrations already covers your job, use it: it is the vendor's route. Cotlet fits when you want ChatGPT, Claude or a script doing the studio paperwork in Pixifi today, from your own login, with nothing to host.
Cotlet is built by Take Group sp. z o.o., registered in Poland, EU (VAT PL6342984273) and in business since 2019, with founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Pixifi tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=pixifi, turn on Pixifi under Integrations in the console and log in at https://www.pixifi.com/admin/ in your Cloud Browser. Then connect your AI agent and ask it about your clients or events. The trial needs no card.
Pixifi publishes no public API documentation: pixifi.com/api answers 404, and in its 1 Nov 2023 webinar Pixifi described its API as bespoke, with keys issued to partner vendors (checked 16 Nov 2026). No Pixifi MCP server and no official ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in Pixifi account.
Pixifi Academy says that on the Essential plan you can only assign yourself to an event, and that Workshops need the Studio Pro plan or higher. The tools follow your plan: they cannot do what your plan does not allow.
No. Pixifi records a refund as a negative payment of type Refund; you issue the money back yourself in Stripe or Square, as Pixifi Academy describes.
The user whose work the agent should do, usually the studio owner. The agent sees only what that user and your plan can see in Pixifi.
Only in how it is called. Both carry the same 38 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Pixifi.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy