Service Fusion · OAuth Scopes

Service Fusion OAuth Scopes

OAuth 2.0 derived

Service Fusion uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://api.servicefusion.com/oauth/access_token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Field Service ManagementFSMHome ServicesContractorsSchedulingDispatchInvoicing

Scopes: 0 Flows: authorizationCode, clientCredentials Method: derived

OAuth endpoints

Authorization URL
https://api.servicefusion.com/oauth/authorize

Token URL
https://api.servicefusion.com/oauth/access_token

Flows
authorizationCodeclientCredentials

Scopes (0)

Service Fusion implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Service Fusion's OAuth 2.0 implementation (authorization_code and client_credentials grants per the official RAML definition at https://docs.servicefusion.com/, and the Connected Apps guide at https://servicefusion.zendesk.com/hc/en-us/articles/360039138891) does not define or document any scopes; access is controlled per connected app via its client credentials, not via granular OAuth scopes.

📄 Provider scope reference: https://docs.servicefusion.com/

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/servicefusion-openapi.yml
docs: https://docs.servicefusion.com/
note: Service Fusion's OAuth 2.0 implementation (authorization_code and client_credentials
  grants per the official RAML definition at https://docs.servicefusion.com/, and the
  Connected Apps guide at https://servicefusion.zendesk.com/hc/en-us/articles/360039138891)
  does not define or document any scopes; access is controlled per connected app via
  its client credentials, not via granular OAuth scopes.
schemes:
- name: oauth2
  source: openapi/servicefusion-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.servicefusion.com/oauth/authorize
    tokenUrl: https://api.servicefusion.com/oauth/access_token
  - flow: clientCredentials
    tokenUrl: https://api.servicefusion.com/oauth/access_token
  description: OAuth 2.0. Access tokens are issued at https://api.servicefusion.com/oauth/access_token.
scopes: []

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
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 scope set

curl "https://apis.io/api/v1/scopes/servicefusion-scopes"

All oauth scopes

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

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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