Fourth · OAuth Scopes

Fourth OAuth Scopes

OAuth 2.0 searched

Fourth publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Fourth API on a user’s behalf.

Tokens are issued from [ROOT]/oauth/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.

CompanyWorkforce ManagementRestaurantsHospitalityInventory ManagementPayrollSchedulingHuman Capital ManagementPoint of SaleFood and Beverage
Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
[ROOT]/oauth/connect/token
Flows
clientCredentials

Scopes (1)

ScopeDescriptionFlows
NotificationService Access to the Fourth Notifications API. clientCredentials

Source

OAuth Scopes

fourth-scopes.yml Raw ↑
generated: '2026-07-19'
method: searched
source: https://developer.fourth.com/en-gb/docs/authenticating-oauth
docs: https://developer.fourth.com/en-gb/docs/authenticating-oauth
schemes:
- name: OAuth2
  flows:
  - flow: clientCredentials
    tokenUrl: '[ROOT]/oauth/connect/token'
scopes:
- scope: NotificationService
  description: Access to the Fourth Notifications API.
  flows: [clientCredentials]
  api: Notifications API
notes: >-
  Fourth documents OAuth scopes per-API on each reference page under the
  Authentication heading; only NotificationService is given as a published
  example in the OAuth guide. Additional per-API scopes exist on the individual
  reference pages but production hosts/specs are not publicly disclosed.