FieldPulse API
FieldPulse documents a REST API spanning roughly 24 resource categories, from jobs and invoices to timesheets and purchase orders. Keys are API-key only and must be requested from support, issued solely to paying customers. Webhooks fire only for job status events.
Frequently asked questions
FieldPulse scores D+ on Supergood's API Report Card. FieldPulse documents a REST API spanning roughly 24 resource categories, from jobs and invoices to timesheets and purchase orders. Keys are API-key only and must be requested from support, issued solely to paying customers. Webhooks fire only for job status events.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
FieldPulse is an all-in-one field service management (FSM) SaaS for residential and commercial trade contractors.
Field Service Management, specifically SMB and lower-mid-market trade contractors with roughly 5–200+ employees. Field technicians use the iOS/Android mobile app to view their daily route, accept dispatched jobs, check in/out, capture photos and notes, build estimates and invoices on site, collect e-signatures, and take payment via FieldPulse Payments or integrated processors.
Medium-to-high within the SMB trade-services FSM segment. Public reviews show meaningful adoption, Capterra/G2/SoftwareAdvice all list hundreds of verified reviews, and the company's own homepage cites 2,537 reviews at 4.8/5.0.
FieldPulse holds the operational and financial system of record for the trade-services businesses that run on it: full customer/contact database, equipment and asset history at each service location, estimates and signed contracts, job and project records with photos and notes, dispatch schedules and technician GPS/timesheet data, inventory and purchase orders, maintenance/service agreement obligations, invoices, payments and FieldPulse Payments processing history, and QuickBooks-synced general-ledger entries.
Mid-life. The current FSM product launched in 2015 (with company origins reported as early as 2009) and has been continuously developed for a decade.
API keys are gated behind manual support requests rather than self-service, and are only issued to paying customers, creating friction for integrators and prospects. Webhooks only fire for job statuses; no event coverage for invoices, payments, customers, estimates, or other core objects, forcing integrators to poll. Full sourced list under Sources below.
Common alternatives include ServiceTitan, Jobber, Housecall Pro, Workiz, FieldEdge, ServiceFusion. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official FieldPulse MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. FieldPulse doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.