Howler · OAuth Scopes

Howler OAuth Scopes

OAuth 2.0 derived

Howler publishes 3 OAuth 2.0 scopes via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Howler API on a user’s behalf.

Tokens are issued from /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.

CompanyEventsTicketingPaymentsCashlessRFIDEvent ManagementFintechSouth Africa

Scopes: 3 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
/oauth/authorize

Token URL
/oauth/token

Flows
authorizationCode

Scopes (3)

Scope	Description	Flows
login	Login scope	authorizationCode
ott	One-time token scope	authorizationCode
public	Public scope	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-19'
method: derived
source: openapi/howler-consumer-portal-openapi.yml
schemes:
- name: oauth2
  source: openapi/howler-consumer-portal-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: /oauth/authorize
    tokenUrl: /oauth/token
  description: OAuth2 authentication for third-party applications
scopes:
- scope: login
  description: Login scope
  flows:
  - authorizationCode
  sources:
  - openapi/howler-consumer-portal-openapi.yml
- scope: ott
  description: One-time token scope
  flows:
  - authorizationCode
  sources:
  - openapi/howler-consumer-portal-openapi.yml
- scope: public
  description: Public scope
  flows:
  - authorizationCode
  sources:
  - openapi/howler-consumer-portal-openapi.yml