Fergus API
Fergus is a cloud job and field service management platform for trades businesses—electricians, plumbers, HVAC, builders, and field service teams—covering quoting, scheduling, job cards, invoicing, payments, and reporting. An unofficial API lets you programmatically pull jobs, quotes, invoices, customers, scheduling, and supplier purchase orders—and push updates like new jobs, quotes, status changes, and invoices back into Fergus.
What is Fergus?
Fergus is a cloud job and field service management platform built for trades businesses—electricians, plumbers, HVAC professionals, builders, roofers, and other field service teams. Tradies use Fergus to generate professional quotes, schedule and assign work on a visual calendar, manage job cards with costs and purchase orders, raise invoices that automatically match costs to jobs, take on-site payments via Tap to Pay, and run profitability and performance reporting—from desktop or the FergusGo mobile app.
Core product areas include:
- Quoting & Estimates (professional quotes, GroundPlan takeoff)
- Scheduling (visual calendar, job assignment, team workload)
- Job Management (job cards, Job Phases, costs, purchase orders, certificates)
- Invoicing & Payments (cost-matched invoices, Tap to Pay on iPhone/Android)
- Reporting & Analytics (profitability, costs, business performance)
- Mobile (FergusGo for iOS and Android), Team Management, and SWMS health & safety forms
Common data entities:
- Jobs, Job Phases, Job Cards, Tasks, Statuses
- Quotes, Estimates, Line Items
- Invoices, Payments, Credit Notes
- Customers, Sites, Contacts
- Purchase Orders, Supplier Invoices, Price Books
- Staff, Schedules, Calendar Events, Time & Materials
The Fergus Integration Challenge
Trades businesses run quoting, scheduling, and invoicing through Fergus every day, but turning those workflows into reliable API-driven automation is non-trivial:
- Mobile-first field data: Much of the work happens in the FergusGo app on phones in the field, so job updates, photos, and timesheets land through mobile flows rather than a clean server-side feed
- Developer access gating: API and developer access is available but typically arranged through Fergus rather than self-serve, so partners face onboarding before they can build
- Supplier and accounting sprawl: Reece, Tradelink, and 40+ suppliers plus Xero, MYOB, and QuickBooks each behave differently, so reconciling purchase orders and invoices across them is messy
- Job lifecycle complexity: Jobs move through quoting, scheduling, work, and invoicing stages with Job Phases—status transitions must be respected, not bypassed
- AU/NZ regional variation: Suppliers, tax handling, and compliance forms (like SWMS) differ between Australia and New Zealand deployments
- Document and certificate handling: Quotes, invoices, certificates, and health & safety forms need careful upload/download and template handling
How Supergood Creates Fergus APIs
Supergood reverse-engineers authenticated browser and app flows, plus Fergus's developer API surface where exposed, to deliver a resilient API layer for your Fergus account—across quoting, scheduling, jobs, and invoicing.
- Handles username/password and MFA securely in a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Jobs, Quotes, Invoices, Customers, and Purchase Orders so you integrate once and rely on consistent objects
- Aligns with AU/NZ supplier, accounting, and compliance specifics to ensure correct reconciliation
Use Fergus with AI agents: Fergus MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your modules, suppliers, accounting stack, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Fergus adapter tailored to your account configuration and region.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Fergus evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Fergus account using username/password or MFA and obtain a session token for downstream calls.
Jobs
/jobsList jobs with filters for status, job phase, customer, site, assigned staff, and date range.
Jobs
/create_jobCreate a new job against a customer and site, including job type, description, and scheduling details.
Quotes
/quotesRetrieve quotes and estimates with line items, totals, and approval status for a job or customer.
Invoicing
/create_invoiceGenerate a cost-matched invoice from a job and sync it to the connected accounting system.
Customers
/customersPull customers, sites, and contacts with associated jobs, quotes, and billing history.
Use Cases
Sync jobs and scheduling into back-office systems
- Pull jobs, statuses, and Job Phases from Fergus into a central warehouse or ops dashboard - Stream schedule and assignment changes to downstream dispatch and workforce tools - Reconcile customer, site, and contact records across Fergus and your CRM
Automate quoting and estimate workflows
- Create quotes and estimates programmatically from inbound leads or takeoff data - Pull quote line items and approval status back for pipeline and forecasting tools - Trigger job creation automatically when a quote is accepted
Reconcile invoices, payments, and accounting
- Sync cost-matched invoices and payments from Fergus into Xero, MYOB, or QuickBooks - Match supplier purchase orders and invoices from Reece, Tradelink, and others against jobs - Surface unpaid invoices and cash-flow events to finance and collections workflows
Drive reporting and profitability analytics
- Extract job costs, time, and materials for profitability and margin reporting - Combine Fergus performance data with other business systems in your BI stack - Trigger alerts when jobs run over budget or fall behind schedule
Technical Specifications
Authentication
Username/password and MFA handled in a managed session
Connectivity
Authenticated browser and app flows plus Fergus's developer API surface where exposed by the account
Response format
Normalized JSON across Jobs, Quotes, Invoices, Customers, and Purchase Order objects
Rate limits
Adaptive throttling tuned to your account to avoid Fergus-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for jobs, quotes, and invoices with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for job status changes, quote acceptance, invoice creation, and payment events
Latency
Sub-second reads on cached entities; multi-second writes when posting jobs, quotes, and invoices
Throughput
Horizontally scaled workers sized to multi-user trades-business job volume
Reliability
Retry, backoff, and idempotency keys for job, quote, and invoice writes
Adaptation
Continuous monitoring of Fergus releases, supplier integrations, and AU/NZ configuration drift
Frequently asked questions
Yes. Supergood works against the authenticated surfaces behind both the web platform and the FergusGo mobile flows, so job updates, timesheets, and photos captured in the field are available through one normalized API.
No. Supergood works with your existing Fergus account and authenticated sessions. We surface a normalized API without requiring you to wait on self-serve developer access, though we complement Fergus's developer API where it is exposed to your account.
Purchase orders, supplier invoices, and accounting records are exposed through the same normalized surface, so you can reconcile data from Reece, Tradelink, and 40+ suppliers alongside Xero, MYOB, and QuickBooks without managing each connection separately.
Yes. Supergood adapts to AU and NZ deployments, accounting for regional suppliers, tax handling, and compliance forms such as SWMS rather than forcing a single generic schema.
The API respects Fergus job statuses and Job Phases, so quoting, scheduling, work, and invoicing transitions are preserved rather than bypassed, keeping your automation consistent with the platform's workflow rules.