Hustle · OAuth Scopes

Hustle OAuth Scopes

OAuth 2.0 derived

Hustle 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.hustle.com/v3/oauth/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.

CompanyEnterpriseMessagingSMSPeer-to-Peer TextingCommunicationsMarketingCivic EngagementWebhooksOAuth
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.hustle.com/v3/oauth/token
Flows
clientCredentials

Scopes (0)

Hustle 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.

📄 Provider scope reference: https://api.hustle.com/v3/docs/

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-19'
method: derived
source: openapi/hustle-openapi-original.json
docs: https://api.hustle.com/v3/docs/
schemes:
- name: OAuth2ClientCredentials
  source: openapi/hustle-openapi-original.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.hustle.com/v3/oauth/token
scopes: []
notes: >-
  The Hustle Public API uses the OAuth2 client-credentials flow and returns a
  `scope` string on the token response, but the spec does not declare a
  components.securitySchemes.flows.clientCredentials.scopes map and no
  per-operation `security[]` scope requirements are present. No enumerable scope
  values are published in the OpenAPI, so the derived scope list is empty by
  design (absence is valid data, not a gap to fabricate). Access is governed by
  the credentials issued to the client rather than a documented scope catalog.