ServiceTitan · OAuth Scopes
ServiceTitan OAuth Scopes
OAuth 2.0
derived
ServiceTitan 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://auth.servicetitan.io/connect/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 ManagementTradesHVACPlumbingElectricalConstructionCRMDispatchAccountingPricebookMarketingMembershipsWebhooks
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://auth.servicetitan.io/connect/token
https://auth.servicetitan.io/connect/token
Flows
clientCredentials
clientCredentials
Scopes (0)
ServiceTitan 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.
ServiceTitan supports only the OAuth 2.0 client_credentials grant and publishes no OAuth scope strings — access is governed by per-app "API scopes" (View/Modify per API resource) selected in the developer portal and approved by the tenant admin (https://developer.servicetitan.io/docs/oauth20/, https://partnerapis.servicetitan.io/docs/create-and-manage-applications/).
ServiceTitan supports only the OAuth 2.0 client_credentials grant and publishes no OAuth scope strings — access is governed by per-app "API scopes" (View/Modify per API resource) selected in the developer portal and approved by the tenant admin (https://developer.servicetitan.io/docs/oauth20/, https://partnerapis.servicetitan.io/docs/create-and-manage-applications/).
📄 Provider scope reference: https://developer.servicetitan.io/docs/oauth20/