Moxie Public API
The Moxie Public API lets you read from and push data into a Moxie workspace — clients, contacts, projects, invoices, payments, time entries, tickets and more. It is the same surface that powers the Moxie Zapier integration.
Every endpoint is exposed under two equivalent path prefixes:
- /public/action/… — for direct API integrations
- /zapier/action/… — used by the Zapier connector
This documentation describes the /public/action/* surface. The request and response shapes are identical on both prefixes.
Conventions
- Base URL: your Moxie API host (e.g.
https://api.withmoxie.com). - All requests authenticate with an
X-API-KEYheader. - Request and response bodies are JSON (
application/json), except file uploads, which usemultipart/form-data. - Many create endpoints resolve related records by name (e.g.
clientName,projectName) rather than by id, creating them where noted. - Dates are ISO-8601 (
YYYY-MM-DDfor dates, RFC-3339 for timestamps).
Endpoints by resource
The reference is organized by the resource each endpoint acts on. Within a resource, list/search endpoints come before the create/action endpoints.
- Clients — list, search, create, update
- Contacts — search, create, update
- Projects & Tasks — search projects, create/update projects, create tasks, approve deliverables
- Invoices & Payments — search payable invoices, create invoices, apply payments
- Expenses — create, update
- Time Tracking — log time entries
- Tickets — create tickets and comments
- Pipeline & Forms — create/update opportunities, form submissions
- Agreements — search (read-only)
- Calendar — create/update and delete events
- Attachments — upload files (multipart or from URL)
- Workspace & Reference Data — account lookup, users, vendors, templates, pipeline/task stages, form names
Start with Authentication, then jump into the reference.