FieldPulse
FieldPulse is an all-in-one field service management (FSM) platform, founded in 2015 and headquartered in Dallas, Texas, serving residential and commercial service contractors across HVAC/R, electrical, plumbing, garage door, locksmith, appliance repair, fire and security, septic, glass, and property management trades. The platform combines scheduling and dispatch, customer and job management, estimates, invoices, payments, purchase orders, material lists, timesheets, projects, custom forms, reporting, and workflow automation, with add-on products for VoIP (Engage), Operator AI, Pricebook, FieldPulse Payments, and fleet tracking. FieldPulse publishes a public REST API — the "Open API", available on the Enterprise plan — documented on a Mintlify docs site with a machine-readable OpenAPI 3.0 definition covering 57 paths and 109 operations across 25 resource areas, authenticated with an x-api-key header issued by support, rate limited to 50 requests per second, plus an outbound webhook surface for job, estimate, and invoice events.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles FieldPulse the way a machine reads it — 59 machine-readable artifacts across 26 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — FieldPulse scores 59.3/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from FieldPulse's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fieldpulse/"
title="FieldPulse on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fieldpulse.svg"
alt="FieldPulse Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fieldpulse/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fieldpulse/"
title="FieldPulse on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fieldpulse/card.svg"
alt="FieldPulse Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile FieldPulse
Each block below is one kind of artifact we hold for FieldPulse. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 26
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
FieldPulse Docs MCP Server
FieldPulse serves an anonymous, publicly reachable Model Context Protocol server from its documentation host at https://help.fieldpulse.com/mcp. The server reports protocol vers...
FieldPulse Assets API
Endpoints related to assets
FieldPulse Assets Category API
Endpoints related to assets category
FieldPulse Comments API
Endpoints related to comments
FieldPulse Company Profile API
Endpoints related to contracts
FieldPulse Contracts API
Endpoints related to contracts
FieldPulse Custom Fields API
Endpoints related to custom fields
FieldPulse Customers API
Endpoints related to customers
FieldPulse Estimates API
Endpoints related to estimates
FieldPulse Invoices API
The Invoices API from FieldPulse — 4 operation(s) for invoices.
FieldPulse Items API
The Items API from FieldPulse — 2 operation(s) for items.
FieldPulse Jobs API
The Jobs API from FieldPulse — 5 operation(s) for jobs.
FieldPulse Lead Source API
The Lead Source API from FieldPulse — 1 operation(s) for lead source.
FieldPulse Locations API
The Locations API from FieldPulse — 2 operation(s) for locations.
FieldPulse Material Lists API
The Material Lists API from FieldPulse — 6 operation(s) for material lists.
FieldPulse Payments API
The Payments API from FieldPulse — 2 operation(s) for payments.
FieldPulse Pipeline Status API
The Pipeline Status API from FieldPulse — 1 operation(s) for pipeline status.
FieldPulse Projects API
The Projects API from FieldPulse — 2 operation(s) for projects.
FieldPulse Purchase Orders API
The Purchase Orders API from FieldPulse — 2 operation(s) for purchase orders.
FieldPulse Subtasks API
The Subtasks API from FieldPulse — 2 operation(s) for subtasks.
FieldPulse Tags API
The Tags API from FieldPulse — 2 operation(s) for tags.
FieldPulse Teams API
The Teams API from FieldPulse — 1 operation(s) for teams.
FieldPulse Timesheets API
The Timesheets API from FieldPulse — 2 operation(s) for timesheets.
FieldPulse Users API
The Users API from FieldPulse — 1 operation(s) for users.
FieldPulse Vendors API
The Vendors API from FieldPulse — 2 operation(s) for vendors.
FieldPulse Version API
The Version API from FieldPulse — 1 operation(s) for version.
Scroll within the panel for all 26 ·
Open Collections 26
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONFieldPulse Assets API
OPEN COLLECTIONFieldPulse Assets Category API
OPEN COLLECTIONFieldPulse Comments API
OPEN COLLECTIONFieldPulse Company Profile API
OPEN COLLECTIONFieldPulse Contracts API
OPEN COLLECTIONFieldPulse Custom Fields API
OPEN COLLECTIONFieldPulse Customers API
OPEN COLLECTIONFieldPulse Estimates API
OPEN COLLECTIONFieldPulse Invoices API
OPEN COLLECTIONFieldPulse Items API
OPEN COLLECTIONFieldPulse Jobs API
OPEN COLLECTIONFieldPulse Lead Source API
OPEN COLLECTIONFieldPulse Locations API
OPEN COLLECTIONFieldPulse Material Lists API
OPEN COLLECTIONFieldPulse Payments API
OPEN COLLECTIONFieldPulse Pipeline Status API
OPEN COLLECTIONFieldPulse Projects API
OPEN COLLECTIONFieldPulse Purchase Orders API
OPEN COLLECTIONFieldPulse Subtasks API
OPEN COLLECTIONFieldPulse Tags API
OPEN COLLECTIONFieldPulse Teams API
OPEN COLLECTIONFieldPulse Timesheets API
OPEN COLLECTIONFieldPulse Users API
OPEN COLLECTIONFieldPulse Vendors API
OPEN COLLECTIONFieldPulse Version API
OPEN COLLECTIONScroll within the panel for all 26 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
fieldpulse-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Fieldpulse Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Fieldpulse Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Fieldpulse Events Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for FieldPulse — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fieldpulse · machine-readable index on apis.io
This is an independent, third-party profile of FieldPulse, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.