FieldPulse API
FieldPulse is a field service management platform for growing home-service and contracting businesses, unifying scheduling, dispatching, estimates, invoicing, payments, inventory, and customer management. An unofficial API lets you programmatically pull customers, jobs, estimates, invoices, projects, payments, and inventory—and push updates like new jobs, estimates, customer records, and pipeline statuses back into FieldPulse.
What is FieldPulse?
FieldPulse is a field service management platform that helps growing service businesses streamline operations through clear processes and customizable workflows across office and field teams. Home-service and contracting companies use FieldPulse to schedule and dispatch technicians, manage jobs and work orders, build estimates and invoices, process payments, track inventory, and run recurring maintenance agreements.
Core product areas include:
- Scheduling & Dispatching (route optimization, technician assignment)
- Job & Work Order Management (job tracking, coordination, custom workflows via ClearPath)
- Estimates & Invoices (quote and billing generation)
- FieldPulse Payments (built-in payment processing)
- Customer Management and Customer Communication
- Project Management, Inventory Management, and Maintenance Agreements
- Dashboards & Reporting (performance analytics and insights)
Common data entities:
- Customers, Locations, Contacts, Tags, Lead Sources, Pipeline Status
- Jobs, Subtasks, Comments, Timesheets, Custom Fields
- Estimates, Invoices, Payments, Material Lists, Purchase Orders
- Projects, Contracts, Assets, Vendors, Teams, Users
The FieldPulse Integration Challenge
Service businesses run mission-critical daily operations on FieldPulse, but turning portal- and mobile-driven workflows into reliable API automation is non-trivial:
- API key by request: Access requires contacting FieldPulse support to obtain a key passed in an x-api-key header—there is no self-serve OAuth onboarding
- Limited webhook coverage: FieldPulse only offers webhooks for job statuses today, so most state changes must be polled
- Rate limits: The API enforces 50 requests per second and returns 429 responses when exceeded, requiring careful client-side throttling
- Read-only resources: Contracts and certain entities support retrieval only, so workflows must account for which objects can be written
- Mobile-first data: Much technician and field activity is captured in the mobile app, complicating headless extraction and reconciliation
- Custom fields and configurable workflows: ClearPath custom workflows and per-account custom fields vary by tenant, so generic integrations drift
How Supergood Creates FieldPulse APIs
Supergood reverse-engineers authenticated FieldPulse sessions and the REST API surface to deliver a resilient, normalized API layer for your FieldPulse account—covering customers, jobs, estimates, invoices, payments, projects, and inventory.
- Manages API key headers, login, and session continuity with automated refresh and change detection
- Respects the 50 req/sec rate limit with adaptive throttling, backoff, and 429 handling
- Normalizes responses across Customers, Jobs, Estimates, Invoices, Payments, and Projects so you integrate once against consistent objects
- Synthesizes change events through polling where native webhooks are unavailable, surfacing job, estimate, and invoice updates
Use FieldPulse with AI agents: FieldPulse MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your FieldPulse modules, entities, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready FieldPulse adapter tailored to your account configuration and custom fields.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as FieldPulse evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a FieldPulse account using an API key passed in the x-api-key header and obtain a managed session for downstream calls.
Customers
/customersList customers with filters for pipeline status, lead source, tags, and location.
Customers
/create_customerCreate a new customer record with contact details, location, and lead source from a third-party CRM or website lead form.
Jobs
/jobsRetrieve jobs and work orders with status, assignment, schedule, and subtask filters.
Jobs
/create_jobCreate a new job against a customer with scheduling, assignment, and custom field values.
Billing
/invoicesPull invoices, estimates, and payments with status and date-range filters for accounting and AR reconciliation.
Use Cases
Sync customers and pipeline status with your CRM
- Create and update FieldPulse customers from a third-party CRM or marketing tool - Push pipeline status and lead source changes to keep sales and field teams aligned - Send website and ad lead data into FieldPulse without manual entry
Automate job and work order workflows
- Create jobs and subtasks from task-management or ticketing systems - Sync comments on jobs and customer records from Slack or Microsoft Teams - Stream job status changes to downstream dashboards and customer notifications
Reconcile estimates, invoices, and payments
- Sync estimates, invoices, and payments into your general ledger and AR systems - Match material lists and purchase orders against job costs - Surface unpaid invoices and overdue accounts to collections workflows
Centralize field operations reporting
- Pull jobs, timesheets, and projects into a single warehouse for analytics - Track technician productivity and route efficiency across teams - Feed inventory and maintenance-agreement data into forecasting tools
Technical Specifications
Authentication
API key passed in the x-api-key header, handled inside a managed Supergood session
Connectivity
FieldPulse REST API plus authenticated session flows where endpoints are not publicly exposed
Response format
Normalized JSON across Customers, Jobs, Estimates, Invoices, Payments, and Projects objects
Rate limits
Adaptive throttling tuned to FieldPulse's 50 requests-per-second limit with automatic 429 backoff
Session management
Automatic session refresh, API key rotation, and credential vaulting
Data freshness
Near real-time pulls for jobs, estimates, and invoices with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Native job-status webhooks passed through, with polling-based change events for estimates, invoices, and customers
Latency
Sub-second reads on cached entities; multi-second writes when posting through job and billing workflows
Throughput
Horizontally scaled workers sized to multi-crew job and invoice volume
Reliability
Retry, backoff, and idempotency keys for job creation, invoicing, and payment transactions
Adaptation
Continuous monitoring of FieldPulse API releases and per-account custom field and workflow drift
Frequently asked questions
FieldPulse issues API keys on request—you contact their support team to obtain a key passed in the x-api-key header. Supergood manages that key inside a secure session so you integrate against a stable, normalized surface.
FieldPulse natively offers webhooks only for job statuses today. Supergood passes those through and synthesizes change events for estimates, invoices, customers, and other entities through efficient polling so you get near real-time updates across the board.
The FieldPulse API enforces a 50 req/sec limit and returns 429 responses when exceeded. Supergood applies adaptive throttling, backoff, and queueing so your integration stays within limits without dropping work.
Customers, jobs, estimates, invoices, payments, projects, material lists, purchase orders, subtasks, and more support create, update, and retrieve actions. Contracts and certain read-only resources support retrieval only, and Supergood maps each entity to its supported operations.
Yes. Supergood profiles your account's custom fields and ClearPath custom workflows, preserving tenant-specific fields and statuses rather than forcing a generic schema.