Create Zuper invoices and quotes/estimate packages via the API
domain: developers.zuper.co · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with your API key against the correct regional host, then POST to the invoice endpoint (/api/invoice) with an invoice object containing line items and customer/work-order references
Use the invoice_estimate/package endpoints to work with quote-like 'packages' tied to an estimate, retrieving package details by UID when needed
Link the invoice to the originating work order so job costing and invoicing stay associated in reporting
Update invoice status as payments are recorded, keeping Zuper in sync with your external accounting/payment system
Re-fetch the invoice after creation to confirm computed totals (tax, discounts) match expectations
Handle the documented 200/400/500 response shapes explicitly, since error payloads carry the validation detail you need for retry logic
Known gotchas
Invoices and estimate 'packages' are separate object types in Zuper's schema — a quote/estimate is not simply an invoice in draft status
As with other Zuper endpoints, requests must target the correct {dc-region} host for the account or they will fail
The invoice creation payload nests fields under a single invoice object — check the current reference schema for required nested fields before assuming a flat payload works
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?