Service Fusion

Service Fusion is field service management (FSM) software for home-service contractors - HVAC, plumbing, electrical, appliance repair, and similar trades. It covers customer management, estimates, scheduling and dispatch, work orders/jobs, invoicing, payments, inventory, and a technician mobile app, with flat-rate pricing and unlimited users on every plan. Service Fusion exposes an Open API - a REST/JSON interface secured with OAuth 2.0 (base https://api.servicefusion.com/v1, token endpoint https://api.servicefusion.com/oauth/access_token) - that lets developers read and create records for customers, jobs, estimates, invoices, technicians, and related resources. API access is available on the Pro plan; the API is rate limited to roughly 60 requests per minute.

Service Fusion publishes 9 API contracts indexed on the APIs.io network, including Calendar Tasks API, Contacts API, Customers API, and 6 more. Tagged areas include Field Service Management, Home Services, Contractors, Scheduling, and Dispatch.

The Service Fusion catalog on APIs.io includes 1 Spectral governance ruleset.

Service Fusion’s developer surface includes authentication, documentation, engineering blog, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.6/100 thin ▬ flat Agent 27/100 agent aware Front door AI 2/6 trace Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

1 published contract

Field Service Management Home Services Contractors Scheduling Dispatch Invoicing

What this lets a business do 3

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Customer Relationship Management

BC-420

ContactsCustomers

GET /customers POST /customers GET /customers/{id}/contacts

Financial Management

BC-200

InvoicesPayments

POST /invoices POST /payments

Sales Management

BC-410

Estimates

POST /estimates

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 28.6/100 · thin

Contract Quality 9.3 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 1.0 / 15

Operational Transparency 0.7 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 2.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/servicefusion/"><img src="https://apis.io/badge/servicefusion/card.svg" alt="Service Fusion on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 6.4 — up to +18.7 composite points Ask about this →
Developer Ergonomics scores 32.1 — up to +13.6 composite points Ask about this →
Contract Quality scores 49.4 — up to +12.7 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/servicefusion/apis.yml: open an issue on github.com/api-evangelist/servicefusion to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Field Service, Home Services and Trades	long-tail	2.5 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Service Fusion Calendar Tasks API

Non-job scheduled calendar items and reminders.

Service Fusion Contacts API

Individual contacts and service locations on a customer account.

Service Fusion Customers API

Customer accounts served by the contractor.

Service Fusion Estimates API

Estimates (quotes) presented to customers before work begins.

Service Fusion Invoices API

Invoices billed to customers for completed work.

Service Fusion Jobs API

Jobs (work orders) scheduled and dispatched to technicians.

Service Fusion Payments API

Payments applied against invoices.

Service Fusion Products and Services API

Catalog of products (parts/inventory) and services (labor/tasks).

Service Fusion Techs and Users API

Technicians and users the work is assigned to.

Scroll for all 9

Open Collections 10

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Service Fusion Open Calendar Tasks API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Contacts API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Customers API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Estimates API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Invoices API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Jobs API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Payments API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Products and Services API

OPEN COLLECTION

Service Fusion Open Calendar Tasks Techs and Users API

OPEN COLLECTION

Service Fusion Open API

OPEN COLLECTION

Scroll for all 10

Service Fusion API pricing

Not yet checked against Service Fusion's own pricing page. Compiled by API Evangelist on 2026-07-03 from www.servicefusion.com/pricing; confirm before you rely on a figure.

Plan	Price
Starter paid	—
Plus paid	—
Pro paid	—

Plan details, limits and sources →

Rate limits

API Requests: ~60 per minute requests
Pagination Page Size: per-page (bounded page size) records
Jobs List Sort Requirement: sort parameter required requests

Compiled by API Evangelist, not yet checked against Service Fusion's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Service Fusion Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Service Fusion Rate Limits

4 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Service Fusion Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Service Fusion API Rules

60 rules · 57 error-severity 2 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Service Fusion Authentication

http/oauth2 · 2 schemes

SECURITY

Service Fusion Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Service Fusion Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Service Fusion Agentic Access

24 operations · 9 acting

AGENTIC

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

LinkedIn

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: servicefusion
url: https://raw.githubusercontent.com/api-evangelist/servicefusion/refs/heads/main/apis.yml
name: Service Fusion
kind: company
description: Service Fusion is field service management (FSM) software for home-service contractors - HVAC, plumbing, electrical,
  appliance repair, and similar trades. It covers customer management, estimates, scheduling and dispatch, work orders/jobs,
  invoicing, payments, inventory, and a technician mobile app, with flat-rate pricing and unlimited users on every plan. Service
  Fusion exposes an Open API - a REST/JSON interface secured with OAuth 2.0 (base https://api.servicefusion.com/v1, token
  endpoint https://api.servicefusion.com/oauth/access_token) - that lets developers read and create records for customers,
  jobs, estimates, invoices, technicians, and related resources. API access is available on the Pro plan; the API is rate
  limited to roughly 60 requests per minute.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/servicefusion.png
tags:
- Field Service Management
- Home Services
- Contractors
- Scheduling
- Dispatch
- Invoicing
tags_raw:
- Field Service Management
- FSM
- Home Services
- Contractors
- Scheduling
- Dispatch
- Invoicing
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.23'
apis:
- aid: servicefusion:servicefusion-calendar-tasks-api
  name: Service Fusion Calendar Tasks API
  description: Non-job scheduled calendar items and reminders.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Calendar Tasks
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-calendar-tasks-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-contacts-api
  name: Service Fusion Contacts API
  description: Individual contacts and service locations on a customer account.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Contacts
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-contacts-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-customers-api
  name: Service Fusion Customers API
  description: Customer accounts served by the contractor.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-customers-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-estimates-api
  name: Service Fusion Estimates API
  description: Estimates (quotes) presented to customers before work begins.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Estimates
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-estimates-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-invoices-api
  name: Service Fusion Invoices API
  description: Invoices billed to customers for completed work.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Invoices
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-invoices-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-jobs-api
  name: Service Fusion Jobs API
  description: Jobs (work orders) scheduled and dispatched to technicians.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Job
  tags_raw:
  - Jobs
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-jobs-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-payments-api
  name: Service Fusion Payments API
  description: Payments applied against invoices.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-products-and-services-api
  name: Service Fusion Products and Services API
  description: Catalog of products (parts/inventory) and services (labor/tasks).
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Products and Services
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-products-and-services-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
- aid: servicefusion:servicefusion-techs-and-users-api
  name: Service Fusion Techs and Users API
  description: Technicians and users the work is assigned to.
  humanURL: https://docs.servicefusion.com/
  baseURL: https://api.servicefusion.com/v1
  tags:
  - Techs and Users
  properties:
  - type: OpenAPI
    url: openapi/servicefusion-techs-and-users-api-openapi.yml
  - type: Documentation
    url: https://docs.servicefusion.com/
  - type: APIReference
    url: https://docs.servicefusion.com/
  - type: PostmanCollection
    url: collections/servicefusion.postman_collection.json
  - type: OpenCollection
    url: collections/servicefusion.opencollection.json
common:
- type: CapabilityMap
  url: capabilities/servicefusion-capability-edges.yml
  name: Service Fusion Business Capability Map
- type: AgenticAccess
  url: agentic-access/servicefusion-agentic-access.yml
- type: DomainSecurity
  url: security/servicefusion-domain-security.yml
- type: Authentication
  url: authentication/servicefusion-authentication.yml
- type: OAuthScopes
  url: scopes/servicefusion-scopes.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/service-fusion
- type: Website
  url: https://www.servicefusion.com
- type: Documentation
  url: https://docs.servicefusion.com/
- type: Plans
  url: plans/servicefusion-plans-pricing.yml
- type: RateLimits
  url: rate-limits/servicefusion-rate-limits.yml
- type: FinOps
  url: finops/servicefusion-finops.yml
- type: Blog
  url: https://www.servicefusion.com/blog/feed/
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Service Fusion API — frequently asked questions

Does Service Fusion have an API?

Yes. APIs.io lists 9 APIs from Service Fusion, including Service Fusion Calendar Tasks API, Service Fusion Contacts API and Service Fusion Customers API, and 6 more.

Is there an OpenAPI specification for the Service Fusion API?

Yes. APIs.io indexes 9 OpenAPI specifications for Service Fusion, each linked for download from this page.

How do I authenticate with the Service Fusion API?

Service Fusion documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Service Fusion Authentication.

How much does the Service Fusion API cost?

APIs.io lists 3 pricing plans for Service Fusion, with each plan's price, limits and inclusions under Pricing on this page.

Is the Service Fusion API ready for AI agents?

Service Fusion has a Kin Score of 28.6 out of 100 (thin) and an Agent Readiness score of 27.1 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/servicefusion"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/servicefusion/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/servicefusion/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.