Query Jobber invoices and their applied payment records via GraphQL
domain: developer.getjobber.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Authenticate and set the X-JOBBER-GRAPHQL-VERSION header, then query the invoice object either directly by ID or nested under a client or job
Request the invoice's payment records field to see payments already applied against it, alongside balance and line item detail
Use invoice-related mutations to create or edit invoices and to record new payments as they come in outside Jobber (e.g. synced from a payment processor)
Paginate nested connections (like a client's invoices) using first/after cursor arguments rather than requesting unbounded lists
Reconcile invoice status (draft, sent, paid, etc.) against your accounting system after each sync run
Check userErrors on every mutation and re-query the invoice afterward to confirm the payment or edit was applied
Known gotchas
Requesting invoices without a first/after argument on a connection field causes the API to assume up to 100 nodes for cost-calculation purposes, which can trigger throttling even if fewer records actually exist
Payment records reflect what's recorded in Jobber — the API does not process payments/settle funds itself
Nested invoice queries under client or job objects add to query cost multiplicatively per node, so keep requested fields minimal in list views
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?