How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Service Fusion Payments API

Payments applied against invoices.

Service Fusion Payments API is one of 9 APIs that Service Fusion publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 1 path, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.servicefusion.com/v1.

2 operations 1 paths 5 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.servicefusion.com/v1
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Service Fusion Payments API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • oauth2 — OAuth 2.0. Access tokens are issued at https://api.servicefusion.com/oauth/accesstoken.
  • bearerAuth — Bearer access token obtained via the OAuth 2.0 token endpoint.

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 2

Payments applied against invoices.

GET
/payments
List payments
listPayments 4 params → 200401
POST
/payments
Record a payment
createPayment body → 201401422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Payment (5 properties), PaymentInput (4 properties), Pagination (3 properties), PaymentList (2 properties). Each schema is shown below with its type and property counts.

Payment
object
5 properties
Error
object
2 properties
PaymentList
object
2 properties
PaymentInput
object
4 properties 2 required
Pagination
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

servicefusion-payments-api-openapi.yml Raw ↑

Other APIs Service Fusion publishes across the network.

Service Fusion Calendar Tasks API
Service Fusion Contacts API
Service Fusion Customers API
Service Fusion Estimates API
Service Fusion Invoices API
Service Fusion Jobs API
Service Fusion Products and Services API
Service Fusion Techs and Users API
Where this information came from

This is an independent, third-party profile of Service Fusion Payments API, 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.